Triple
T31612526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Imperial of Mexico |
E806663
|
entity |
| Predicate | hasNoDeFactoHolder |
P202742
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Prince Imperial of Mexico, hasNoDeFactoHolder, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoDeFactoHolder Context triple: [Prince Imperial of Mexico, hasNoDeFactoHolder, true]
-
A.
holderIsNotNecessarily
Indicates that the entity identified as the holder of something does not have to possess or satisfy a specified property, role, or condition.
-
B.
hasSuccessiveHolders
Indicates that one entity has a sequence of different entities that have held the same role, position, or status one after another over time.
-
C.
officeHolderNotRequired
Indicates that holding a particular office or position is not mandatory for the related role, action, or status to apply.
-
D.
holderIs
Indicates that one entity serves as the holder, possessor, or container of another entity.
-
E.
hasHolderRight
Indicates that one entity possesses a legal or formal right over another entity or resource.
- 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_69f348d61f2081908cad94bc9ffbb671 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a00b34364448190b8c9948d5a24d845 |
completed | May 10, 2026, 4:33 p.m. |
| PD | Predicate disambiguation | batch_6a00b2e4f13c819081bac7d763c414ad |
completed | May 10, 2026, 4:31 p.m. |
| PDg | Predicate description generation | batch_6a00b342b39c8190b54d6d85ddafb085 |
completed | May 10, 2026, 4:33 p.m. |
Created at: April 30, 2026, 10:37 p.m.