Triple
T34723638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hungduan Ifugao language |
E1000986
|
entity |
| Predicate | primaryUsageCommunity |
P7159
|
FINISHED |
| Object | rural communities in Hungduan |
—
|
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: rural communities in Hungduan | Statement: [Hungduan Ifugao language, primaryUsageCommunity, rural communities in Hungduan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryUsageCommunity Context triple: [Hungduan Ifugao language, primaryUsageCommunity, rural communities in Hungduan]
-
A.
usedByCommunity
chosen
Indicates that something is utilized or adopted collectively by a particular community.
-
B.
coreCommunity
Indicates that an entity belongs to the central or most essential group within a larger community.
-
C.
primaryUsersOf
Indicates that the subject is the main or most frequent user(s) of the object.
-
D.
communityUsage
Indicates how something is used, adopted, or engaged with by a particular community or group of people.
-
E.
primaryUseOf
Indicates that one entity serves as the main or principal function, purpose, or application of another 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_69f76daeb6e48190a4c9a6b0edc80f72 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 3:59 p.m.