Triple
T26865604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles de France |
E676456
|
entity |
| Predicate | housePosition |
P162000
|
FINISHED |
| Object | younger son of King Charles X 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: younger son of King Charles X of France | Statement: [Charles de France, housePosition, younger son of King Charles X of France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: housePosition Context triple: [Charles de France, housePosition, younger son of King Charles X of France]
-
A.
houseLocatedIn
Indicates that a house is situated within or belongs to a specific geographic location or area.
-
B.
houseElement
Indicates that one entity is a structural or functional component of a house associated with another entity.
-
C.
houseResult
Indicates the outcome or status produced by a housing-related process, event, or decision involving the referenced entities.
-
D.
housesIcon
Indicates that one entity serves as the icon or symbolic graphical representation for another entity.
-
E.
house2
Indicates a relationship where one entity is a secondary, related, or alternative house associated with another entity.
- F. None of above. chosen
Provenance (4 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_69eee9ba94bc8190b44c5d4397d04ecd |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f622abdfac8190988421c946411d7e |
completed | May 2, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621c7d3e0819095b1f327637ae4f9 |
completed | May 2, 2026, 4:09 p.m. |
Created at: April 27, 2026, 5:28 a.m.