Triple
T18536937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Williamsburgh Savings Bank Tower |
E452988
|
entity |
| Predicate | wasTallestFrom |
P125522
|
FINISHED |
| Object | 1929 |
—
|
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: 1929 | Statement: [Williamsburgh Savings Bank Tower, wasTallestFrom, 1929]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasTallestFrom Context triple: [Williamsburgh Savings Bank Tower, wasTallestFrom, 1929]
-
A.
replacedByAsTallest
Indicates that one entity has superseded another as the tallest among a relevant group or category.
-
B.
wasTallestBuildingFromYear
chosen
Indicates that a building held the status of being the tallest building starting from a specified year.
-
C.
wasTallestBuildingUntilYear
Indicates that a building held the status of being the tallest building up to, but not beyond, a specified year.
-
D.
heldTallestStructureTitleUntil
Indicates that one structure held the title of being the tallest in a given context up to and including a specified end time.
-
E.
heldTallestStructureTitleFrom
Indicates that an entity held the title of being the tallest structure for a specified time period starting from a given point.
- 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_69d8d387b5548190aa030dad2cb4947e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5340256d08190bf22d2cb064413b2 |
completed | April 19, 2026, 7:58 p.m. |
| PD | Predicate disambiguation | batch_69e469e0025c81908f16ed4f922674af |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:37 a.m.