Triple
T5297839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Vietnamese đồng |
E119898
|
entity |
| Predicate | replacedByAtUnification |
P63884
|
FINISHED |
| Object | liberation đồng |
—
|
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: liberation đồng | Statement: [South Vietnamese đồng, replacedByAtUnification, liberation đồng]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedByAtUnification Context triple: [South Vietnamese đồng, replacedByAtUnification, liberation đồng]
-
A.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by another entity.
-
B.
replacedByDuringRecovery
Indicates that one entity is substituted or superseded by another specifically for the duration of a recovery period.
-
C.
replacedWith
Indicates that one entity has been substituted or superseded by another entity, taking over its role, function, or position.
-
D.
mayBeReplacedBy
Indicates that one entity can potentially be substituted or superseded by another entity.
-
E.
replacedBecause
Indicates that one entity has been substituted for another specifically due to a particular reason or cause.
- 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_69bd446f22b88190b6a47fb91c68a3e7 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd8e44e7c881909b241b2fec366038 |
completed | March 20, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69bd845097ac81909678624c4907fda4 |
completed | March 20, 2026, 5:30 p.m. |
| PDg | Predicate description generation | batch_69bd8e43c4c88190bb72b9bf56c99425 |
completed | March 20, 2026, 6:13 p.m. |
Created at: March 20, 2026, 1:53 p.m.