Triple
T18676856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tapestry of Nations |
E456621
|
entity |
| Predicate | successorOpeningDate |
P132254
|
FINISHED |
| Object | 2001-09-10 |
—
|
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: 2001-09-10 | Statement: [Tapestry of Nations, successorOpeningDate, 2001-09-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorOpeningDate Context triple: [Tapestry of Nations, successorOpeningDate, 2001-09-10]
-
A.
plannedOpeningDate
Indicates the date on which something is scheduled or intended to begin operating or become available.
-
B.
officialOpeningDate
Indicates the calendar date on which something is formally inaugurated or officially opened for use or operation.
-
C.
openingDay
Indicates the specific day on which something, typically an event, season, or venue, officially begins or first opens to the public.
-
D.
successionYear
Indicates the calendar year in which one entity formally succeeded or took over from another in a given role, position, or status.
-
E.
rerAOpeningDate
Indicates the date on which something (such as a facility, service, or route) is opened again after having been closed.
- 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_69d8d38f72b4819090a935175d9ca8af |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e556b66680819082a268f1bf857db5 |
completed | April 19, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69e478db7a248190a8c6584673773923 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484133ee48190a80f1889d79f34c9 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:48 a.m.