Triple
T37544694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southmen |
E933427
|
entity |
| Predicate | originallyPlannedCity |
P21398
|
FINISHED |
| Object | Toronto, Ontario |
E1525
|
NE 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: Toronto, Ontario | Statement: [Southmen, originallyPlannedCity, Toronto, Ontario]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyPlannedCity Context triple: [Southmen, originallyPlannedCity, Toronto, Ontario]
-
A.
originallyPlannedFor
Indicates that something was initially intended, designed, or scheduled to be used for or associated with a particular purpose, event, or entity, regardless of what ultimately occurred.
-
B.
plannedToConnectCity
Indicates that an entity had the intention or made arrangements to establish a connection or link between cities.
-
C.
hasPlannedCity
chosen
Indicates that an entity has a city that was deliberately designed and constructed according to a prearranged plan.
-
D.
destinationCity
Indicates the city to which an entity is traveling, being sent, or ultimately directed.
-
E.
cityOfOriginal
Indicates the city from which something or someone originally comes or was first created or established.
- F. None of above.
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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40cda759ec819098200c989248476d |
completed | June 28, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.