Triple
T8970875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hero of Yaguajay |
E214261
|
entity |
| Predicate | hasCanonicalHolderCount |
P86003
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Hero of Yaguajay, hasCanonicalHolderCount, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCanonicalHolderCount Context triple: [Hero of Yaguajay, hasCanonicalHolderCount, 1]
-
A.
hasCanonicalNumber
Indicates that an entity is associated with its officially recognized or standard reference number.
-
B.
hasCanonicalPosition
Indicates that an entity occupies a standard, officially recognized, or authoritative position or location within a defined structure or system.
-
C.
hasCurrentHolder
Indicates that a specified entity is the present holder, possessor, or occupant of another entity (such as a position, title, asset, or object).
-
D.
hasCanonicalRepresentation
Indicates that one entity is the standard or authoritative form in which another entity is represented.
-
E.
hasFirstHolder
Indicates that an entity is associated with the earliest or original holder (e.g., owner, position-bearer, or title-holder) of something.
- 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_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. |
| PDg | Predicate description generation | batch_69cc5fcf24348190b6b845205161c0ee |
completed | March 31, 2026, 11:59 p.m. |
Created at: March 30, 2026, 7:02 p.m.