Triple
T23454035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austria |
E567867
|
entity |
| Predicate | railConnectionWith |
P74180
|
FINISHED |
| Object | Hungary |
—
|
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: Hungary | Statement: [Austria, railConnectionWith, Hungary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railConnectionWith Context triple: [Austria, railConnectionWith, Hungary]
-
A.
railConnectionPurpose
Indicates the intended function or goal of a particular rail connection between locations or networks.
-
B.
railwayConnectsTo
Indicates that one railway line, track, or network is directly linked or joined to another, allowing trains to move between them.
-
C.
countryRailConnection
chosen
Indicates that there is a railway connection or service linking two countries.
-
D.
connectsToRailStation
Indicates that one entity has a direct link, route, or access connection to a rail station.
-
E.
hasPassengerRailConnection
Indicates that there exists a passenger rail service linking one location or transport node to another.
- 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_69e2458b4c888190b1d7998f9862a558 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a695fed08190bfa160e69200546d |
completed | April 29, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:53 p.m.