Triple
T11564531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seoul–New York |
E274221
|
entity |
| Predicate | connectsFinancialCenters |
P100364
|
FINISHED |
| Object | true |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: true | Statement: [Seoul–New York, connectsFinancialCenters, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsFinancialCenters Context triple: [Seoul–New York, connectsFinancialCenters, true]
-
A.
connectsBank
Indicates a relationship where one entity serves to link or provide access between another entity and a bank or banking service.
-
B.
associatedFort
Indicates that one entity is connected or linked to a particular fort, typically as its related or corresponding fortification.
-
C.
isReferralCenterFor
Indicates that one entity serves as a designated center to which other entities send or direct cases, clients, or tasks for specialized services or handling.
-
D.
managingCenter
Indicates that one entity serves as the administrative or coordinating center responsible for managing another entity or activity.
-
E.
hasFinancialInstitution
Indicates that one entity is associated with or linked to a financial institution, such as a bank or similar financial service provider.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d6aae5ac3c81908d2b0a3a665665b2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d88dd321f88190a57ecaf079fbbc3f |
completed | April 10, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69d85dc3fc2c8190bed7e2111301a77c |
completed | April 10, 2026, 2:17 a.m. |
| PDg | Predicate description generation | batch_69d87f2e67108190ac36bf47aac12fa8 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 8, 2026, 9:37 p.m.