Triple
T32864852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orang Kanaq |
E840620
|
entity |
| Predicate | countryOfficialTerm |
P202346
|
FINISHED |
| Object | Orang Asli |
—
|
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: Orang Asli | Statement: [Orang Kanaq, countryOfficialTerm, Orang Asli]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryOfficialTerm Context triple: [Orang Kanaq, countryOfficialTerm, Orang Asli]
-
A.
countryOfficial
Indicates that an entity serves as the official or legally recognized country associated with another entity.
-
B.
countryOfficialUse
Indicates that a country officially uses, recognizes, or adopts a particular entity (such as a language, currency, or symbol) in an official capacity.
-
C.
representsCountryOfficialName
Indicates that an entity is the official, legally recognized country name of another entity.
-
D.
associatedCountryOfficialName
Indicates that an entity is linked to the official, formal name of a specific country with which it is associated.
-
E.
governingCountryOfficialName
Indicates the official name of the country that exercises governing authority over a given entity.
- 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_69f34942465c819099b3fb47f9044f58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0075be7f54819081ab12bc1dab53bb |
completed | May 10, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_6a0073a19030819098c23faa3adcb96e |
completed | May 10, 2026, 12:01 p.m. |
| PDg | Predicate description generation | batch_6a0075bd35e08190b604777ae9fbbe4b |
completed | May 10, 2026, 12:10 p.m. |
Created at: May 1, 2026, 1:17 a.m.