Triple
T34952054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jan Lucemburský |
E1008025
|
entity |
| Predicate | přenesenyOstatky |
P66523
|
FINISHED |
| Object | katedrála sv. Víta v Praze |
—
|
NE NERFINISHED |
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: katedrála sv. Víta v Praze | Statement: [Jan Lucemburský, přenesenyOstatky, katedrála sv. Víta v Praze]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: přenesenyOstatky Context triple: [Jan Lucemburský, přenesenyOstatky, katedrála sv. Víta v Praze]
-
A.
remainsTransferredTo
chosen
Indicates that the physical remains of an entity are moved or handed over from one party, place, or custodian to another.
-
B.
transferredWith
Indicates that something was moved or conveyed from one entity to another using a specified medium, method, or accompanying item.
-
C.
transferredUnder
Indicates that something is moved, conveyed, or reassigned from one party, context, or control to another under specified terms or conditions.
-
D.
remnants
Indicates that parts or traces of something remain after the main portion has been removed, used, or destroyed.
-
E.
exchangedFor
Indicates that one entity has been traded or substituted in return for another entity.
- 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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782cea4c881908ada116c80eafa15 |
completed | May 3, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69f781020cc4819088c40cb8589504e4 |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.