Triple
T5745287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Subanen |
E126716
|
entity |
| Predicate | traditionalLeader |
P66493
|
FINISHED |
| Object | timuay |
—
|
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: timuay | Statement: [Subanen, traditionalLeader, timuay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalLeader Context triple: [Subanen, traditionalLeader, timuay]
-
A.
leaderIsUsually
Indicates that an entity typically serves as the leader in relation to another entity or within a given context.
-
B.
supportedLeader
Indicates that one entity actively backed, endorsed, or provided assistance to a particular leader.
-
C.
mainLeader3
Indicates that an entity serves as the third primary or most prominent leader within a specified group, organization, or context.
-
D.
mainLeaders
Indicates that the referenced entities serve as the primary or most important leaders within a group, organization, or context.
-
E.
theoreticalLeader
Indicates a relationship where one entity is regarded as the leader in theory or principle, but does not necessarily hold or exercise actual leadership in practice.
- F. None of above. chosen
Provenance (4 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_69c0083179548190b384b0bf3c08ca4d |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b52663c8190ab44258468d4296d |
completed | March 22, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69c021ca61688190875bd6107161c284 |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c02b4ea03c81908c3d799462de20c4 |
completed | March 22, 2026, 5:47 p.m. |
Created at: March 22, 2026, 3:48 p.m.