Triple
T28051490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Count of Cervera |
E708831
|
entity |
| Predicate | hasHeirApparentConnection |
P87163
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Count of Cervera, hasHeirApparentConnection, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeirApparentConnection Context triple: [Count of Cervera, hasHeirApparentConnection, yes]
-
A.
hasHeirApparentFunction
Indicates that an entity has a designated heir apparent role or function assigned to it.
-
B.
hasHeirApparentTitle
Indicates that an entity holds a title designating them as the officially recognized heir apparent to another entity’s position or rank.
-
C.
hasHeirPresumptiveEligibility
Indicates that an entity is recognized as having a current, but potentially displaceable, right to inherit or succeed to a position, title, or estate.
-
D.
isHeirExpectedBy
Indicates that one entity is anticipated or designated to inherit from, succeed, or receive rights from another entity.
-
E.
consideredHeirApparent
chosen
Indicates that one entity is regarded or treated as the likely or expected successor to another entity, typically in a position of authority or inheritance.
- 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_69ef9b6df9f48190bbb971d02cbe1b65 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 27, 2026, 8:33 p.m.