Triple
T7322941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leopold Georg Christian Friedrich |
E168794
|
entity |
| Predicate | dynastyRole |
P25666
|
FINISHED |
| Object | founder of the Belgian royal dynasty |
—
|
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: founder of the Belgian royal dynasty | Statement: [Leopold Georg Christian Friedrich, dynastyRole, founder of the Belgian royal dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynastyRole Context triple: [Leopold Georg Christian Friedrich, dynastyRole, founder of the Belgian royal dynasty]
-
A.
dynasticRole
chosen
Indicates the specific position, function, or status an entity holds within a dynasty or hereditary ruling line.
-
B.
dynasty
Indicates a hereditary ruling line or family that holds power over a state or territory across successive generations.
-
C.
leadershipDynasty
Indicates a succession relationship where leadership is passed down within the same family or ruling line over time.
-
D.
dynastyContext
Indicates the historical or cultural dynasty within which an entity, event, or relationship is situated or contextualized.
-
E.
dynastyServed
Indicates that a person or group rendered service or allegiance to a particular ruling 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_69c68a54cacc81908e3b773441f19566 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f0446628819093e96236f1aa4a9b |
completed | March 27, 2026, 9:01 p.m. |
| PD | Predicate disambiguation | batch_69c6e77230048190b2c29ca6b3a65b8e |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:03 p.m.