Triple
T37570186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashipa |
E934667
|
entity |
| Predicate | rankInCouncil |
P192019
|
FINISHED |
| Object | notable chief |
—
|
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: notable chief | Statement: [Ashipa, rankInCouncil, notable chief]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankInCouncil Context triple: [Ashipa, rankInCouncil, notable chief]
-
A.
rankIn
Indicates the relative position or level an entity holds within an ordered set, hierarchy, or competitive context.
-
B.
rankInStateCouncil
Indicates the position or level an individual holds within a specific state's council hierarchy.
-
C.
eligibleRank
Indicates that an entity meets the required rank or level criteria to qualify for a specific role, action, or benefit.
-
D.
rankWithinCouncilDocuments
Indicates the relative ordering or importance assigned to a document compared to other documents within the same council’s collection.
-
E.
nobleRankIn
Indicates that an entity holds a specified noble rank within a particular political or territorial jurisdiction.
- 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_69f76ecd99148190be327e391a70f5b6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
| PDg | Predicate description generation | batch_69fcf1b241888190a243f07051c71383 |
completed | May 7, 2026, 8:10 p.m. |
Created at: May 3, 2026, 4:17 p.m.