Triple
T32254466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manhattan Life Insurance Building |
E823973
|
entity |
| Predicate | surpassed |
P42712
|
FINISHED |
| Object | New York World Building |
—
|
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: New York World Building | Statement: [Manhattan Life Insurance Building, surpassed, New York World Building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surpassed Context triple: [Manhattan Life Insurance Building, surpassed, New York World Building]
-
A.
surpasses
chosen
Indicates that one entity exceeds or goes beyond another in degree, quality, performance, or achievement.
-
B.
overcomes
Indicates that one entity successfully prevails against, defeats, or gains control over another entity or opposing force.
-
C.
overtook
Indicates that one entity moved past and ahead of another that was previously in front, typically while both were in motion.
-
D.
surpassedStructure
Indicates that one entity has exceeded or gone beyond another entity in terms of structural capacity, performance, or advancement.
-
E.
superior
Indicates that one entity holds a higher rank, status, or level of authority than another entity.
- 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_69f3490db0748190bfef6e50c95d39d3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bc52a83481909b3a4a9f8181b4bd |
completed | May 3, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:41 a.m.