Triple
T4244529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cambodian riel |
E95495
|
entity |
| Predicate | reintroducedReplacing |
P29646
|
FINISHED |
| Object | Kampuchean riel |
—
|
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: Kampuchean riel | Statement: [Cambodian riel, reintroducedReplacing, Kampuchean riel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reintroducedReplacing Context triple: [Cambodian riel, reintroducedReplacing, Kampuchean riel]
-
A.
reintroduced
Indicates that an entity that was previously removed, extinct, or absent has been brought back or restored to a place, context, or state.
-
B.
replacedWith
chosen
Indicates that one entity has been substituted or superseded by another entity, taking over its role, function, or position.
-
C.
replacedDuring
Indicates that one entity took the place of another entity during a specified time period or interval.
-
D.
reintroducedFrom
Indicates that an entity has been brought back or restored from a specified prior source, context, or location after having been removed, lost, or discontinued.
-
E.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by 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_69b3453d91548190b4d4ef8fe52aa2ac |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e8c42e88190b309a1ef7f6529ac |
completed | March 12, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69b347f587148190a1830503459939b6 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:05 p.m.