Triple
T30499380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toronto city boundary |
E776095
|
entity |
| Predicate | definesExtentOf |
P51731
|
FINISHED |
| Object | City of 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: City of Toronto | Statement: [Toronto city boundary, definesExtentOf, City of Toronto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesExtentOf Context triple: [Toronto city boundary, definesExtentOf, City of Toronto]
-
A.
originalExtent
Indicates the total size or scope that something initially had before any reduction, alteration, or loss.
-
B.
extent
Indicates the degree, scope, or magnitude to which a property, condition, or relationship holds.
-
C.
maximumExtent
Indicates the greatest or furthest degree, size, or range to which something can extend or apply within a given context.
-
D.
directionalExtent
Indicates the directional span or reach of something from a reference point, specifying how far it extends along a particular direction.
-
E.
currentExtentDesignated
chosen
Indicates that the currently applicable spatial or conceptual extent of something has been formally defined or designated.
- F. None of above.
Provenance (3 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_69f22498c5d481908aaea89e6fab8280 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: April 29, 2026, 8:14 p.m.