Triple
T34952042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jan Lucemburský |
E1008025
|
entity |
| Predicate | korunovace |
P181887
|
FINISHED |
| Object | 1311-02-07 |
—
|
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: 1311-02-07 | Statement: [Jan Lucemburský, korunovace, 1311-02-07]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: korunovace Context triple: [Jan Lucemburský, korunovace, 1311-02-07]
-
A.
rok
Indicates a generic, unspecified relationship or interaction between entities labeled by this predicate.
-
B.
kokudaka
Indicates a relationship where a landholding or domain is assigned a value based on its assessed agricultural productivity or tax yield, typically measured in koku.
-
C.
rukus
Indicates that an entity is associated with or participates in a disturbance, commotion, or noisy disruptive event involving another entity.
-
D.
kurumOdağı
Indicates a focus on or orientation toward an institution, organization, or corporate entity in the context of the described relationship or action.
-
E.
outran
Indicates that one entity ran faster than another and moved ahead of them in a race or chase.
- F. None of above. chosen
Provenance (4 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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782cf61948190b98185d961609554 |
completed | May 3, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69f781020cc4819088c40cb8589504e4 |
completed | May 3, 2026, 5:08 p.m. |
| PDg | Predicate description generation | batch_69f782c848fc8190baea8c845ca9079f |
completed | May 3, 2026, 5:15 p.m. |
Created at: May 3, 2026, 4 p.m.