Triple
T35239881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luitpoldings |
E1017481
|
entity |
| Predicate | lostDucalPower |
P157255
|
FINISHED |
| Object | 10th century |
—
|
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: 10th century | Statement: [Luitpoldings, lostDucalPower, 10th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lostDucalPower Context triple: [Luitpoldings, lostDucalPower, 10th century]
-
A.
lostDucalTitle
Indicates that an entity that once held a ducal title has had that title taken away, relinquished, or otherwise ceased to possess it.
-
B.
lostThroneTo
Indicates that one entity was previously in possession of a throne or rulership but was defeated or displaced so that another entity took that throne instead.
-
C.
lastDukeBeforeKingship
Indicates that the subject was the final holder of the ducal title immediately prior to the establishment or assumption of kingship.
-
D.
lostDuchyOfNassauTo
Indicates that one party ceased to control the Duchy of Nassau, which was taken over or acquired by another party.
-
E.
lostSupremacyAfter
chosen
Indicates that one entity ceased to hold a position of dominance or superiority over another entity following a specific event or point in time.
- 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_69f76de235048190b990070c23c51b6b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.