Triple
T34952033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jan Lucemburský |
E1008025
|
entity |
| Predicate | otec |
P181884
|
FINISHED |
| Object | Jindřich VII. Lucemburský |
—
|
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: Jindřich VII. Lucemburský | Statement: [Jan Lucemburský, otec, Jindřich VII. Lucemburský]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: otec Context triple: [Jan Lucemburský, otec, Jindřich VII. Lucemburský]
-
A.
to
Indicates a directional or goal-oriented relationship in which something is directed, transferred, or oriented toward a target or endpoint.
-
B.
terminus
Indicates that one entity serves as the final endpoint or stopping place for another entity’s movement, route, or process.
-
C.
tür
Indicates that one entity is a type, kind, or category of another entity.
-
D.
tgp
Indicates a temporal grouping or period-based association between entities, such as items or events linked by a shared time span or phase.
-
E.
ターミナル設備
Indicates a relationship where terminal facilities (such as stations, ports, or terminals) are provided, used, or involved as key infrastructure in a transportation or logistics context.
- 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.