Triple
T24196661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNTAC |
E599851
|
entity |
| Predicate | refugeesRepatriated |
P50603
|
FINISHED |
| Object | over 360000 Cambodian refugees |
—
|
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: over 360000 Cambodian refugees | Statement: [UNTAC, refugeesRepatriated, over 360000 Cambodian refugees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refugeesRepatriated Context triple: [UNTAC, refugeesRepatriated, over 360000 Cambodian refugees]
-
A.
repatriatedBy
Indicates that an entity is brought or returned back to its country or place of origin by a specified agent or authority.
-
B.
repatriatedOn
Indicates that something or someone was returned to their country or place of origin on a specific date or time.
-
C.
returnedFromDeportation
Indicates that an entity has come back to a place or jurisdiction after previously being deported from it.
-
D.
repatriationCountryTo
chosen
Indicates the country to which someone or something is returned or sent back, typically to their place of origin or citizenship.
-
E.
repatriationStatus
Indicates the current state or progress of returning a person or asset back to their country or original place of origin.
- 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_69e288ceaab88190899d0acb5931591d |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e24ad83c819084ac9e34d2cc2120 |
completed | April 29, 2026, 10:49 a.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:36 p.m.