Triple
T37992554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toronto—Danforth |
E947854
|
entity |
| Predicate | borderSouth |
P117551
|
FINISHED |
| Object | Lake Ontario |
—
|
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: Lake Ontario | Statement: [Toronto—Danforth, borderSouth, Lake Ontario]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderSouth Context triple: [Toronto—Danforth, borderSouth, Lake Ontario]
-
A.
boundaryTypeSouth
Indicates the type or nature of the boundary that lies to the south of a given entity.
-
B.
borderCountrySide
Indicates that one country shares a land border with the side or region of another country.
-
C.
borderRegion
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
-
D.
hasSouthBorder
chosen
Indicates that one entity shares its southern boundary or border with another entity.
-
E.
borderRegime
Indicates the type, rules, or control system governing how movement or interaction is managed across a border between entities.
- 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_69f76efa37088190be5416b7ef1ca275 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a002103c93081908398fa5726f5fa6e |
completed | May 10, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_6a001fcb9fb48190a27d8f2ca983fbe6 |
completed | May 10, 2026, 6:03 a.m. |
Created at: May 3, 2026, 4:20 p.m.