Triple
T20973275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchess of Savoy |
E516555
|
entity |
| Predicate | linkedDynasties |
P95093
|
FINISHED |
| Object | French nobility |
—
|
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: French nobility | Statement: [Duchess of Savoy, linkedDynasties, French nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedDynasties Context triple: [Duchess of Savoy, linkedDynasties, French nobility]
-
A.
dynasticallyLinkedTo
chosen
Indicates a relationship where two entities are connected through a line of succession, inheritance, or familial rule within or across dynasties.
-
B.
formedDynasty
Indicates that an entity established or created a ruling dynasty.
-
C.
associatedWithDynasty
Indicates that an entity has a historical, political, cultural, or familial connection to a specific dynasty.
-
D.
associatedDynasticOrder
Indicates a relationship where an entity is linked to, or formally connected with, a particular dynastic order.
-
E.
countryOfDynasticConnection
Indicates that there exists a historical dynastic link—such as through ruling families, royal marriages, or shared dynasties—between the subject and the referenced country.
- 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_69e0b4fee5ac8190875fa9ceba1a5e5e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fba2406c8190bd75dec585c14bfa |
completed | April 21, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69e5dbe6976081908abd4e9c8734bae9 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:45 p.m.