Triple
T35212127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord of Bañares |
E1016709
|
entity |
| Predicate | nobleTitleRealm |
P123375
|
FINISHED |
| Object | Kingdom of Castile |
—
|
NE NERFINISHED |
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: Kingdom of Castile | Statement: [Lord of Bañares, nobleTitleRealm, Kingdom of Castile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nobleTitleRealm Context triple: [Lord of Bañares, nobleTitleRealm, Kingdom of Castile]
-
A.
royalTitularyFeature
Indicates that something is a characteristic or component element of a royal titulary (the formal set of titles held by a monarch).
-
B.
nobleTitleHeirTo
Indicates that one entity is the designated heir to the noble title held by another entity.
-
C.
nobleTitleOrStatus
chosen
Indicates that one entity holds, claims, or is associated with a particular noble rank, title, or social status in relation to another entity.
-
D.
isRoyalTitle
Indicates that something is a formal title associated with royalty or a royal rank.
-
E.
kingConsortOfTitle
Indicates that a male monarch holds the position of king consort corresponding to a specific noble or royal title.
- 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_69f76ddf549c8190869d0af076fd2c28 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.