Triple
T9890790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quadrilateral Security Dialogue |
E181443
|
entity |
| Predicate | revivalYear |
P91011
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [Quadrilateral Security Dialogue, revivalYear, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revivalYear Context triple: [Quadrilateral Security Dialogue, revivalYear, 2017]
-
A.
reversionYear
Indicates the year in which something returns to a previous state, condition, or ownership.
-
B.
rediscoveryYear
Indicates the year in which something that was previously known but lost, forgotten, or overlooked was found or recognized again.
-
C.
revivalVersionProducedFor
Indicates that a specific version of a revived work (such as a reboot, remake, or updated edition) was produced for a particular entity, context, or release.
-
D.
periodOfRevival
Indicates a time span during which something that had declined or been inactive experiences renewed growth, activity, or prominence.
-
E.
reconstructionYear
Indicates the year in which something was rebuilt, restored, or reconstructed after damage, alteration, or destruction.
- 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_69ca8283a6708190801af7a25a7ebb9f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb47dfa908190884e96e5e5d6f41f |
completed | April 2, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69cd1d872d50819096b7ab166a8decf1 |
completed | April 1, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69cd3581a9688190a00cef4c3eebb0ae |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:39 p.m.