Triple
T29972579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaro (village head) |
E761358
|
entity |
| Predicate | isTraditionalRoleIn |
P11687
|
FINISHED |
| Object | Kanekes |
—
|
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: Kanekes | Statement: [Jaro (village head), isTraditionalRoleIn, Kanekes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTraditionalRoleIn Context triple: [Jaro (village head), isTraditionalRoleIn, Kanekes]
-
A.
isKeyRole
Indicates that an entity holds a primary or critically important role within a given context or structure.
-
B.
isPrincipalRoleIn
Indicates that an entity holds the primary or leading role in a particular context, work, or relationship.
-
C.
servesRole
chosen
Indicates that one entity performs, fulfills, or occupies a particular function, position, or responsibility in relation to another entity.
-
D.
hasStructureRole
Indicates that an entity serves a specific functional or positional role within a larger structure or organizational arrangement.
-
E.
hasLegalRole
Indicates that an entity holds a specific legal capacity, status, or function in relation to another entity or 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_69f22467626081908d5afea489590e96 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 6:32 p.m.