Triple
T20097141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Louis of Saxe-Coburg-Saalfeld |
E496429
|
entity |
| Predicate | memberOfDynastyProducing |
P91745
|
FINISHED |
| Object | European monarchs |
—
|
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: European monarchs | Statement: [Prince Louis of Saxe-Coburg-Saalfeld, memberOfDynastyProducing, European monarchs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberOfDynastyProducing Context triple: [Prince Louis of Saxe-Coburg-Saalfeld, memberOfDynastyProducing, European monarchs]
-
A.
associatedWithDynasty
Indicates that an entity has a historical, political, cultural, or familial connection to a specific dynasty.
-
B.
partOfDynasty
chosen
Indicates that an entity belongs to, or is a constituent member of, a particular dynasty.
-
C.
formedDynasty
Indicates that an entity established or created a ruling dynasty.
-
D.
refersToPersonWithDynasty
Indicates that one entity makes reference to a person specifically identified or characterized by their association with a particular dynasty.
-
E.
associatedWithDynastyFoundation
Indicates a relationship in which an entity is connected to the founding or establishment of a particular dynasty.
- 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_69da626eee3881909f3454986d4a6511 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6666d83448190b3ade3f5b855e820 |
completed | April 20, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69e54cf788188190a46cc49c9ce7617f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:25 p.m.