Triple
T240166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nguyen Van Thieu |
E4912
|
entity |
| Predicate | causeOfEndOfPosition |
P6707
|
FINISHED |
| Object | defeat of South Vietnam in 1975 |
—
|
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: defeat of South Vietnam in 1975 | Statement: [Nguyen Van Thieu, causeOfEndOfPosition, defeat of South Vietnam in 1975]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfEndOfPosition Context triple: [Nguyen Van Thieu, causeOfEndOfPosition, defeat of South Vietnam in 1975]
-
A.
reasonForEndOfTerm
chosen
Indicates the specific cause or circumstance that led to the termination or conclusion of a term, position, or period of service.
-
B.
positionA
Indicates the spatial or ordered position of an entity A within a defined reference frame or sequence.
-
C.
positionB
Indicates that one entity occupies or is located at a specific position relative to another entity.
-
D.
causeOfChangeOfDestination
Indicates that one entity is the reason or trigger for another entity changing its intended destination.
-
E.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
- 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_69a257c3d0708190b0871c4269d273e6 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d35aa288190966b6e15af1525cb |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b60ad308190b12f119960a8bde7 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.