Triple
T18988709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Avon |
E464622
|
entity |
| Predicate | hasHeirMaleRequirement |
P15554
|
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: [Earl of Avon, hasHeirMaleRequirement, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeirMaleRequirement Context triple: [Earl of Avon, hasHeirMaleRequirement, yes]
-
A.
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.
-
B.
hasHeirApparentFunction
Indicates that an entity has a designated heir apparent role or function assigned to it.
-
C.
hasGenderRequirement
chosen
Indicates that a particular role, activity, or context specifies a required or restricted gender for participation or eligibility.
-
D.
notUsedIfMonarchHasNoDaughters
Indicates that this relationship or rule does not apply in cases where the monarch has no daughters.
-
E.
requiresCelibacyFor
Indicates that one entity imposes a requirement of celibacy on another entity as a condition for participation, membership, role, or status.
- 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_69d8dd008af48190a97ff1c6488edf1b |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d66272388190850a7e5dec165a01 |
completed | April 20, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f88e0c81908cb20f08bf24cd32 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:01 p.m.