Triple
T33383602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oroquieta |
E854850
|
entity |
| Predicate | hasSecondaryEthnolinguisticGroup |
P115409
|
FINISHED |
| Object | Subanen people |
—
|
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: Subanen people | Statement: [Oroquieta, hasSecondaryEthnolinguisticGroup, Subanen people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondaryEthnolinguisticGroup Context triple: [Oroquieta, hasSecondaryEthnolinguisticGroup, Subanen people]
-
A.
ethnolinguisticGroups
Indicates a relationship where groups are categorized or associated based on shared ethnic and linguistic characteristics.
-
B.
ethnicGroupsIncluded
Indicates that certain ethnic groups are encompassed, represented, or counted within a specified larger group, category, or context.
-
C.
containedEthnicGroup
Indicates that one entity (typically a larger group, region, or population) includes or encompasses a particular ethnic group within it.
-
D.
hasEthnolinguisticPresence
chosen
Indicates that a particular ethnolinguistic group is present or represented within a specified place, context, or population.
-
E.
otherEthnicGroup
Indicates that one entity belongs to a different ethnic group than the other 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_69f3496d54048190a1cb91fdd7caa6ea |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff7c96e6dc8190b89554480ebcea39 |
completed | May 9, 2026, 6:27 p.m. |
| PD | Predicate disambiguation | batch_69ff7c2381748190ad9a2176e0e478cd |
completed | May 9, 2026, 6:25 p.m. |
Created at: May 1, 2026, 1:35 a.m.