Triple
T3352192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John of Bohemia |
E70520
|
entity |
| Predicate | reignEndAsCountOfLuxembourg |
P2721
|
FINISHED |
| Object | 1346 |
—
|
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: 1346 | Statement: [John of Bohemia, reignEndAsCountOfLuxembourg, 1346]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignEndAsCountOfLuxembourg Context triple: [John of Bohemia, reignEndAsCountOfLuxembourg, 1346]
-
A.
successorAsGrandDukeOfLuxembourg
Indicates that one person became the next Grand Duke of Luxembourg following another person in that role.
-
B.
predecessorAsGrandDukeOfLuxembourg
Indicates that one entity previously held the position of Grand Duke of Luxembourg immediately before the other entity.
-
C.
reignDuration
Indicates the length of time during which an entity held ruling or governing authority over a domain or group.
-
D.
endOfReign
chosen
Indicates the point in time or event at which a ruler’s or leader’s period of authority or reign concludes.
-
E.
populationRankInLuxembourg
Indicates the relative position of a place in Luxembourg when ordered by the size of its population.
- 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_69ad85a4ef7c8190a29e2bbd6fa454e4 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb221a7d8819086cd0f826eca0fe8 |
completed | March 8, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69ada42fbe7c8190b9f185b5ab985f17 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:12 p.m.