Triple
T26262436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Punan |
E656887
|
entity |
| Predicate | umbrellaTermFor |
P127829
|
FINISHED |
| Object | various Punan subgroups |
—
|
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: various Punan subgroups | Statement: [Punan, umbrellaTermFor, various Punan subgroups]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: umbrellaTermFor Context triple: [Punan, umbrellaTermFor, various Punan subgroups]
-
A.
brandUmbrella
Indicates that one brand functions as an overarching or parent brand under which another brand is grouped or marketed.
-
B.
classificationTerm
Indicates that one entity serves as a categorical label or type used to classify or group another entity.
-
C.
collectiveTermUsed
chosen
Indicates that one entity is used as a collective term referring to a group or class of other entities.
-
D.
typicalTerm
Indicates that something is a standard, representative, or characteristic term typically associated with a given concept or context.
-
E.
usedTerm
Indicates that one entity employed, referenced, or applied a particular term in some context.
- 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_69ee5b4e21bc819082be98bc9ab09796 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60e00b03c81909d04a9821907dc0d |
completed | May 2, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 9:10 p.m.