Triple
T14206043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Cambridge (1362 creation) |
E352096
|
entity |
| Predicate | hasHolderBirthOrder |
P20593
|
FINISHED |
| Object | younger son of the king |
—
|
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: younger son of the king | Statement: [Earl of Cambridge (1362 creation), hasHolderBirthOrder, younger son of the king]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHolderBirthOrder Context triple: [Earl of Cambridge (1362 creation), hasHolderBirthOrder, younger son of the king]
-
A.
positionInFamilyBirthOrder
chosen
Indicates the relative order in which a person was born within their family (e.g., first-born, middle child, last-born).
-
B.
heldByMotherOf
Indicates that something is possessed, owned, or physically held by the mother of a given entity.
-
C.
hasHolderFather
Indicates that an entity has a father who serves as the holder or custodian of that entity.
-
D.
positionInLineOfSuccessionAtBirth
Indicates the ordinal place an individual held in a defined line of succession at the moment of their birth.
-
E.
firstHolderMother
Indicates that the first holder in a given context is the mother of the related entity.
- 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_69d827894ac0819097803e57f3227b23 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61f84f288190877116330bd54393 |
completed | April 14, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69de05bcd7d48190a4848d9320404aa6 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:05 a.m.