Triple
T7852304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Cambridge, 2nd Marquess of Cambridge |
E182084
|
entity |
| Predicate | hasNoMaleHeir |
P48008
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [George Cambridge, 2nd Marquess of Cambridge, hasNoMaleHeir, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoMaleHeir Context triple: [George Cambridge, 2nd Marquess of Cambridge, hasNoMaleHeir, true]
-
A.
hadNoSurvivingChildren
Indicates that the person did not have any children who were alive at the relevant point in time.
-
B.
extinctionOfMaleLine
chosen
Indicates that a family’s direct male lineage has ended, with no surviving male descendants to continue it.
-
C.
notUsedIfMonarchHasNoDaughters
Indicates that this relationship or rule does not apply in cases where the monarch has no daughters.
-
D.
hasNoAutomaticSuccessionRight
Indicates that an entity does not possess an inherent or legally recognized right to automatically succeed another entity in a role, position, or entitlement.
-
E.
notPrimaryHeir
Indicates that the referenced person is explicitly not the main or principal heir in an inheritance or succession context.
- 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_69ca82869ee08190b8f9040dbc2c0467 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb18ec48548190960bd564a60effa8 |
completed | March 31, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69cae92180f88190ae3d44c3de7adc93 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:51 p.m.