Triple
T32763506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ontario–New York border |
E837822
|
entity |
| Predicate | nearCityOnOntarioSide |
P175091
|
FINISHED |
| Object | Toronto |
—
|
NE NERFINISHED |
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 | Statement: [Ontario–New York border, nearCityOnOntarioSide, Toronto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearCityOnOntarioSide Context triple: [Ontario–New York border, nearCityOnOntarioSide, Toronto]
-
A.
TorontoSection
Indicates a relationship where something is identified as a specific section, division, or part associated with Toronto.
-
B.
directionFromOttawa
Indicates the cardinal or relative compass direction in which one entity is located from Ottawa.
-
C.
hasNearbyCityOnOhioSide
Indicates that an entity has a nearby city located on the Ohio side of a relevant geographic or political boundary.
-
D.
distanceFromBarrie
Indicates the spatial distance separating something from the location of Barrie.
-
E.
isInEasternOntario
Indicates that one entity (typically a place or region) is located within the geographic area known as Eastern Ontario.
- 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_69f34939857c8190aa9970c51feec1eb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6cee547108190ad3bc84297d8f516 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6ce6c76bc8190b865343d3f5810c9 |
completed | May 3, 2026, 4:26 a.m. |
Created at: May 1, 2026, 1:13 a.m.