Triple
T32254468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manhattan Life Insurance Building |
E823973
|
entity |
| Predicate | surpassedDate |
P174448
|
FINISHED |
| Object | 1894 |
—
|
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: 1894 | Statement: [Manhattan Life Insurance Building, surpassedDate, 1894]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surpassedDate Context triple: [Manhattan Life Insurance Building, surpassedDate, 1894]
-
A.
permittedAfterDate
Indicates that an action or condition is allowed to occur only on or after a specified date.
-
B.
secondReachedDate
Indicates the date on which the second specified event, state, or condition is reached or occurs.
-
C.
hasDateWith
Indicates that one entity is scheduled to go on or is engaged in a romantic or social date with another entity.
-
D.
notEarlierThan
Indicates that one event, time, or state does not occur before another, i.e., it is simultaneous with or later than the referenced point.
-
E.
usedToDate
Indicates that two entities were previously in a romantic or dating relationship but are no longer together.
- 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_69f3490db0748190bfef6e50c95d39d3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c2451e108190a73ccfdc99203d55 |
completed | May 3, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c1b666188190ac43c3011a7df048 |
completed | May 3, 2026, 3:32 a.m. |
Created at: May 1, 2026, 12:41 a.m.