Triple
T27113800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Six |
E686784
|
entity |
| Predicate | TorontoSection |
P161864
|
FINISHED |
| Object | Special Presentations |
—
|
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: Special Presentations | Statement: [Mr. Six, TorontoSection, Special Presentations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: TorontoSection Context triple: [Mr. Six, TorontoSection, Special Presentations]
-
A.
terminusCanada
Indicates that something serves as an endpoint, destination, or terminal location within or specifically for Canada.
-
B.
directionFromOttawa
Indicates the cardinal or relative compass direction in which one entity is located from Ottawa.
-
C.
distanceFromToronto
Indicates the spatial distance between a given entity and the location of Toronto.
-
D.
regionCanada
Indicates that an entity is located in, associated with, or pertains to the geographic region of Canada.
-
E.
regionCanadianSide
Indicates that the specified region is located on the Canadian side of a border or boundary.
- 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_69ef148accd48190b6ed6e13a15f2a4f |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6240450088190af486dbde3daeacb |
completed | May 2, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61fa35ac48190890102c348ed81a0 |
completed | May 2, 2026, 4 p.m. |
Created at: April 27, 2026, 8:55 a.m.