Triple
T33496617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GySEV |
E857879
|
entity |
| Predicate | sharesBorderOperationsWith |
P200772
|
FINISHED |
| Object | ÖBB |
—
|
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: ÖBB | Statement: [GySEV, sharesBorderOperationsWith, ÖBB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesBorderOperationsWith Context triple: [GySEV, sharesBorderOperationsWith, ÖBB]
-
A.
shareBorderAgreement
Indicates that two entities have a formally recognized agreement concerning their shared border.
-
B.
shareBorderBetween
Indicates that two geographic or political entities have a common boundary where their territories directly touch.
-
C.
sharesBorderingNetworkWith
Indicates that two entities are connected through adjacent or directly neighboring positions within the same network structure.
-
D.
sharesBorderWithOffice
Indicates that one entity’s boundary directly adjoins or touches the boundary of an office.
-
E.
sharesBorderWithConceptually
Indicates that one entity is conceptually adjacent to another, such that their ideas, domains, or categories touch or overlap like neighboring regions on a map.
- 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_69f3497660508190a541826a81f7e9ab |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ffac35ac5481908b6bdfd5bbe8c76e |
completed | May 9, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69ffabbfd2548190964c851496bbbaee |
completed | May 9, 2026, 9:48 p.m. |
| PDg | Predicate description generation | batch_69ffac34c5948190be36de5781d91da3 |
completed | May 9, 2026, 9:50 p.m. |
Created at: May 1, 2026, 1:38 a.m.