Triple
T33583550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Semai people |
E860215
|
entity |
| Predicate | officialCategory |
P62481
|
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: [Semai people, officialCategory, Orang Asli]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialCategory Context triple: [Semai people, officialCategory, Orang Asli]
-
A.
officialCategoryIn
chosen
Indicates that an entity is formally classified within a specific official category or grouping in a given system or context.
-
B.
canonicalCategory
Indicates that an entity is assigned to its primary or standard category within a classification system.
-
C.
designationCategory
Indicates the classification or type of designation assigned to an entity within a broader designation system.
-
D.
officerCategory
Indicates the classification or type of officer role that an individual holds within an organization or system.
-
E.
official
Indicates that an entity holds an authorized or formally recognized role, status, or capacity within an institution, organization, or governing framework.
- 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_69f3497e70e48190951c94d072879bec |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff7bc112088190851501fb2a16103d |
completed | May 9, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69ff7b45507c81909753866ad733601a |
completed | May 9, 2026, 6:21 p.m. |
Created at: May 1, 2026, 1:40 a.m.