Triple
T34847547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magna Plaza |
E1004510
|
entity |
| Predicate | formerFunctionEndDate |
P140
|
FINISHED |
| Object | 1987 |
—
|
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: 1987 | Statement: [Magna Plaza, formerFunctionEndDate, 1987]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerFunctionEndDate Context triple: [Magna Plaza, formerFunctionEndDate, 1987]
-
A.
deFactoEndDate
Indicates the date on which a relationship, status, or condition effectively ended in practice, regardless of any formal or official end date.
-
B.
finalTerminationDate
Indicates the date on which an agreement, contract, or relationship is conclusively and irrevocably ended.
-
C.
setsTermEndDateFor
Indicates setting or assigning the end date of a term or period for another entity.
-
D.
holderEndDate
Indicates the date on which an entity’s role as holder of something (e.g., an asset, position, or right) comes to an end.
-
E.
endDate
chosen
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
- 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_69f76dba76f0819090643cba102c41ec |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a002e71bdc48190b922f2d3b362d259 |
completed | May 10, 2026, 7:06 a.m. |
| PD | Predicate disambiguation | batch_6a002e1a28708190b65f9e657c770bab |
completed | May 10, 2026, 7:04 a.m. |
Created at: May 3, 2026, 4 p.m.