Triple
T25081866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Murud |
E628206
|
entity |
| Predicate | relatedGroupCategory |
P127424
|
FINISHED |
| Object | Lun Bawang–Kelabit–Murud cluster |
—
|
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: Lun Bawang–Kelabit–Murud cluster | Statement: [Murud, relatedGroupCategory, Lun Bawang–Kelabit–Murud cluster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedGroupCategory Context triple: [Murud, relatedGroupCategory, Lun Bawang–Kelabit–Murud cluster]
-
A.
relatedClassification
chosen
Indicates a relationship where one classification is associated with, linked to, or otherwise contextually connected to another classification.
-
B.
subgroupCategory
Indicates that one category functions as a more specific subgroup within the scope of another, broader category.
-
C.
coveredGroup
Indicates that one group or set is included within, or has its members protected or accounted for by, another group or arrangement.
-
D.
representedGroups
Indicates that an entity serves as an official or recognized representative for one or more groups.
-
E.
coreCategory
Indicates that one entity is the primary or fundamental category to which another entity belongs or is classified under.
- 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_69e2ff2e73f881909992bf3eda5c25cb |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 18, 2026, 6:22 a.m.