Triple
T7330046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princesse Royale |
E168974
|
entity |
| Predicate | appliesToPositionInBirthOrder |
P20593
|
FINISHED |
| Object | eldest daughter |
—
|
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: eldest daughter | Statement: [Princesse Royale, appliesToPositionInBirthOrder, eldest daughter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToPositionInBirthOrder Context triple: [Princesse Royale, appliesToPositionInBirthOrder, eldest daughter]
-
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.
positionInLineOfSuccessionAtBirth
Indicates the ordinal place an individual held in a defined line of succession at the moment of their birth.
-
C.
appliesToBirths
Indicates that something (such as a rule, policy, condition, or attribute) is relevant or applicable specifically to births.
-
D.
appliesToPosition
Indicates that something (such as a rule, condition, or attribute) is relevant or applicable to a specific position or role.
-
E.
appliesToPersonBirthName
Indicates that the referenced value is used as the birth name of the specified person.
- 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_69c68a54cacc81908e3b773441f19566 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f0a9c0f081909218560d8a4f4995 |
completed | March 27, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69c6e77230048190b2c29ca6b3a65b8e |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:03 p.m.