Triple
T5974498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Huéscar |
E132950
|
entity |
| Predicate | titleHolderStatus |
P3783
|
FINISHED |
| Object | heir apparent |
—
|
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: heir apparent | Statement: [Duke of Huéscar, titleHolderStatus, heir apparent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleHolderStatus Context triple: [Duke of Huéscar, titleHolderStatus, heir apparent]
-
A.
titleHolderIs
Indicates that one entity currently holds or possesses a specific title associated with another entity.
-
B.
titleHolderIsUsually
Indicates that an entity serving as a title holder is typically or most commonly a particular type or category of entity.
-
C.
titleStatus
chosen
Indicates the current legal or administrative state of a title (such as ownership, validity, or processing stage) in relation to an entity or record.
-
D.
titleHolderType
Indicates the specific role or capacity in which an entity holds a title (e.g., owner, trustee, beneficiary).
-
E.
titleHolderBelongsTo
Indicates that the holder of a title is associated with or belongs to a particular entity, such as an organization, position, or domain.
- 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_69c0086deab081908550159ca23eec9b |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04dc2243c8190bd3488e7b24af985 |
completed | March 22, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69c049dcb3c081908ccc9b4d4b210229 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:03 p.m.