Triple
T5747565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Edmonton Mall |
E126769
|
entity |
| Predicate | formerRecordHeldUntil |
P37609
|
FINISHED |
| Object | 2004 |
—
|
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: 2004 | Statement: [West Edmonton Mall, formerRecordHeldUntil, 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerRecordHeldUntil Context triple: [West Edmonton Mall, formerRecordHeldUntil, 2004]
-
A.
recordHeldFrom
Indicates that a record or position was held by an entity starting from a specified point in time.
-
B.
recordHeldUntil
chosen
Indicates that a record remained valid, in force, or applicable up to a specified end time or condition.
-
C.
heldTitleUntil
Indicates that an entity possessed or held a specific title or position continuously up to a particular end date or point in time.
-
D.
remainedInForceUntil
Indicates that a rule, condition, or state continued to be valid or effective up to a specified point in time.
-
E.
recordHeld
Indicates that one entity possesses or maintains a particular record associated with another entity or context.
- 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_69c0083179548190b384b0bf3c08ca4d |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b52663c8190ab44258468d4296d |
completed | March 22, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69c021ca61688190875bd6107161c284 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:48 p.m.