Triple
T26325386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cieszyn Silesia dispute |
E662237
|
entity |
| Predicate | concernsInfrastructure |
P54339
|
FINISHED |
| Object | Košice–Bohumín Railway |
—
|
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: Košice–Bohumín Railway | Statement: [Cieszyn Silesia dispute, concernsInfrastructure, Košice–Bohumín Railway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concernsInfrastructure Context triple: [Cieszyn Silesia dispute, concernsInfrastructure, Košice–Bohumín Railway]
-
A.
hasInfrastructureConcern
Indicates that an entity has a problem, risk, or issue related to infrastructure that requires attention or management.
-
B.
relatedInfrastructure
Indicates that one piece of infrastructure is connected, associated, or functionally related to another infrastructure element.
-
C.
infrastructureNeed
Indicates that an entity requires the development, improvement, or provision of infrastructure to meet its functional or operational needs.
-
D.
infrastructureFocusArea
Indicates the specific aspect or domain of infrastructure that an entity, project, or activity is primarily concerned with or directed toward.
-
E.
infrastructureImpact
chosen
Indicates the effect that an action, event, or entity has on the condition, performance, or availability of infrastructure systems.
- 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_69ee812f32748190871d970c4e2a8ddf |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 26, 2026, 10:30 p.m.