Triple
T5974499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Huéscar |
E132950
|
entity |
| Predicate | precedenceWithinHouse |
P1803
|
FINISHED |
| Object | highest title of the heir |
—
|
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: highest title of the heir | Statement: [Duke of Huéscar, precedenceWithinHouse, highest title of the heir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precedenceWithinHouse Context triple: [Duke of Huéscar, precedenceWithinHouse, highest title of the heir]
-
A.
confersPrecedenceIn
Indicates that one entity is granted higher priority, rank, or standing over another within a specified context or domain.
-
B.
sharesPrecedenceWith
Indicates that two entities occupy the same level in an ordering or hierarchy, such that neither has priority or precedence over the other.
-
C.
successorInHouse
Indicates that one entity directly follows another in holding a position or role within the same house or lineage.
-
D.
orderPrecedence
chosen
Indicates that one entity must come before another in a defined sequence or priority order.
-
E.
housePrefectStatus
Indicates the role or standing of an individual in relation to serving as a house prefect within an organization or institution.
- 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.