Triple
T8970876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hero of Yaguajay |
E214261
|
entity |
| Predicate | holderRankAtTime |
P34755
|
FINISHED |
| Object | rebel commander |
—
|
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: rebel commander | Statement: [Hero of Yaguajay, holderRankAtTime, rebel commander]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holderRankAtTime Context triple: [Hero of Yaguajay, holderRankAtTime, rebel commander]
-
A.
lastHolderRank
Indicates the rank or position held by the most recent entity that possessed or held a given item, title, or role.
-
B.
rankAtOpening
Indicates the position or level an entity holds within an ordered ranking at the initial or starting point of a specified period or event.
-
C.
rankStatus
chosen
Indicates the hierarchical level or position an entity holds within an ordered ranking or status system.
-
D.
rankingMember
Indicates that one entity is the highest-ranking or most senior member within a particular group, committee, or organization relative to the others.
-
E.
highestRankIn
Indicates that one entity holds the top or most senior rank within a specified group, category, or context relative to other entities.
- 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_69ca839dbf608190a2f5990477115d29 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc67672c108190919ae6ca69b6291f |
completed | April 1, 2026, 12:31 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed9a2d48190ad11381078e823b7 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:02 p.m.