Triple
T30050392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louise of France |
E763584
|
entity |
| Predicate | placeInHierarchy |
P5163
|
FINISHED |
| Object | daughter of the King of France |
—
|
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: daughter of the King of France | Statement: [Louise of France, placeInHierarchy, daughter of the King of France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeInHierarchy Context triple: [Louise of France, placeInHierarchy, daughter of the King of France]
-
A.
positionInHierarchy
chosen
Indicates that one entity occupies a specific rank or level relative to another within an ordered hierarchy.
-
B.
placeInSeries
Indicates the position or order that something occupies within a sequence or series.
-
C.
seatInHierarchy
Indicates that one entity occupies a specific position or level within an ordered hierarchy relative to other entities.
-
D.
hierarchyProperty
Indicates a relationship where one property is defined as being above, below, or otherwise ordered relative to another property within a structured hierarchy.
-
E.
placementIn
Indicates that one entity is located or positioned within the spatial or structural bounds of another 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_69f22470a89c8190be7273297c0e0d19 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: April 29, 2026, 6:55 p.m.