Triple
T11353963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old City Hall |
E268904
|
entity |
| Predicate | wasTorontoCityHallUntil |
P17716
|
FINISHED |
| Object | 1965 |
—
|
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: 1965 | Statement: [Old City Hall, wasTorontoCityHallUntil, 1965]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasTorontoCityHallUntil Context triple: [Old City Hall, wasTorontoCityHallUntil, 1965]
-
A.
usedAsCityHallUntil
chosen
Indicates that a building or location functioned as the city hall up to a specified end date or time period.
-
B.
usedAsCityHallFrom
Indicates that a building or location functioned as the official city hall of a municipality during a specified time period.
-
C.
wasTallestBuildingInNewYorkUntil
Indicates that a building held the status of being the tallest building in New York up to a specified point in time.
-
D.
hasCityHall
Indicates that a location or administrative area possesses or is served by a specific city hall building or institution.
-
E.
wasLargestMunicipalBuildingIn
Indicates that a building held the status of being the largest municipal building within a specified place or jurisdiction.
- 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_69d6aacbe18081909e5fadb50082dd96 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d80148e2048190a716b515d78efdd1 |
completed | April 9, 2026, 7:43 p.m. |
| PD | Predicate disambiguation | batch_69d7e6f8aeb4819080476f16a69b2ee3 |
completed | April 9, 2026, 5:50 p.m. |
Created at: April 8, 2026, 9:33 p.m.