Triple
T5063983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Germany and Austria |
E114097
|
entity |
| Predicate | shareTransportLinks |
P5346
|
FINISHED |
| Object | cross-border rail connections |
—
|
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: cross-border rail connections | Statement: [Germany and Austria, shareTransportLinks, cross-border rail connections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shareTransportLinks Context triple: [Germany and Austria, shareTransportLinks, cross-border rail connections]
-
A.
sharesRouteWith
Indicates that two entities follow or operate along the same or overlapping route.
-
B.
sharesPlatformWith
Indicates that two entities operate on, are available through, or participate within the same platform or system.
-
C.
sharesIn
Indicates that one entity holds or possesses shares or ownership stakes in another entity.
-
D.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
E.
sharesInteractionPointWith
chosen
Indicates that two entities have at least one common point or location at which they can interact or make contact with each other.
- 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_69bd443c0c8c81908663b77afb28e165 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd747756bc8190863c426e6fd6e8f7 |
completed | March 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69bd715622b48190a3e8e49a5ef62b4a |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:38 p.m.