Triple
T35640928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Čierna nad Tisou |
E1029856
|
entity |
| Predicate | railGaugeConnection |
P5070
|
FINISHED |
| Object | standard gauge (1435 mm) |
—
|
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: standard gauge (1435 mm) | Statement: [Čierna nad Tisou, railGaugeConnection, standard gauge (1435 mm)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railGaugeConnection Context triple: [Čierna nad Tisou, railGaugeConnection, standard gauge (1435 mm)]
-
A.
railwayGaugeContext
Indicates the specific track gauge standard or measurement that applies to, or is used in, a given railway-related context.
-
B.
usesRailGauge
chosen
Indicates that one entity (typically a railway system or line) operates using the specified rail gauge measurement of the other entity.
-
C.
railTracks
Indicates that one entity consists of, includes, or is associated with rail tracks used for guiding trains or rail vehicles.
-
D.
railInterface
Indicates a connection or interaction between entities via a rail-based system or interface.
-
E.
railStandard
Indicates that something conforms to, uses, or is governed by a particular railway or rail transport standard.
- 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_69f76e087bdc8190a4794bf9c0bd7634 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79f4ba54481908718e54775ed46e5 |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4d885881908a3612e2e75cf84f |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.