Triple
T34952050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jan Lucemburský |
E1008025
|
entity |
| Predicate | spojenec |
P145724
|
FINISHED |
| Object | Filip VI. Francouzský |
—
|
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: Filip VI. Francouzský | Statement: [Jan Lucemburský, spojenec, Filip VI. Francouzský]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spojenec Context triple: [Jan Lucemburský, spojenec, Filip VI. Francouzský]
-
A.
повʼязанеЗ
Indicates a general association or connection between one entity and another.
-
B.
sojusznik
chosen
Indicates that one entity is an ally or supportive partner of another entity, typically cooperating toward shared goals or interests.
-
C.
nositelé
Indicates that certain entities serve as bearers or carriers of a specified property, role, or characteristic.
-
D.
unites
Indicates that one entity brings together multiple entities into a single, cohesive whole or shared state.
-
E.
bridged
Indicates that one entity has formed a connection or link that spans across or over another entity, effectively joining two previously separated points.
- 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.