Triple
T33922036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reunification Express line |
E869639
|
entity |
| Predicate | reopenedAfterConflict |
P34772
|
FINISHED |
| Object | Vietnam War |
—
|
NE NERFINISHED |
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: Vietnam War | Statement: [Reunification Express line, reopenedAfterConflict, Vietnam War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reopenedAfterConflict Context triple: [Reunification Express line, reopenedAfterConflict, Vietnam War]
-
A.
reopenedAfter
chosen
Indicates that an entity was closed or inactive and then opened or made active again following a specified prior event or time.
-
B.
reopenedAfterReconstruction
Indicates that a place or facility resumed operations after undergoing reconstruction or major rebuilding work.
-
C.
reopenedFor
Indicates that an entity, previously closed or inactive, has been opened again to allow access, use, or operation for another entity or purpose.
-
D.
reopenedAfterStabilization
Indicates that something previously closed or inactive was opened or resumed again after conditions had stabilized or become sufficiently secure.
-
E.
previousConflict
Indicates that a conflict or dispute occurred between the entities at some earlier time prior to the current 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_69f349992c508190aa4afa24a086cc8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7064e906881909c3186c646145d34 |
completed | May 3, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69f70100ec1c8190a6b97f50e88891f2 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:49 a.m.