Triple
T761530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess of Orange |
E16079
|
entity |
| Predicate | heirStatus |
P2940
|
FINISHED |
| Object | heir apparent |
—
|
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: heir apparent | Statement: [Princess of Orange, heirStatus, heir apparent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heirStatus Context triple: [Princess of Orange, heirStatus, heir apparent]
-
A.
heirOf
Indicates that one entity is the legal or designated successor who inherits from another entity, typically upon that entity’s death or transfer of rights.
-
B.
successionLawStatus
Indicates the legal status or condition governing how succession or inheritance is determined or applied.
-
C.
heirApparentOf
chosen
Indicates that one entity is the officially recognized primary successor who is expected to inherit a title, position, or role from another entity.
-
D.
heirPresumptive
Indicates a person who is first in line to inherit a title, position, or estate but whose claim can be displaced by the birth of a more eligible heir.
-
E.
hasHeirApparentTitle
Indicates that an entity holds a title designating them as the officially recognized heir apparent to another entity’s position or rank.
- 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_69a493684ee48190bd43b7c78da4aec8 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a682e7d081909c9cd7839a49fb0b |
completed | March 1, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69a4a5048a8081908d0542214142664a |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.