Triple
T28351520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naumburg tramway |
E718110
|
entity |
| Predicate | trackGaugeComparedToStandard |
P69893
|
FINISHED |
| Object | narrower than standard gauge |
—
|
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: narrower than standard gauge | Statement: [Naumburg tramway, trackGaugeComparedToStandard, narrower than standard gauge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackGaugeComparedToStandard Context triple: [Naumburg tramway, trackGaugeComparedToStandard, narrower than standard gauge]
-
A.
trackGauge
Indicates the distance between the inner faces of the rails in a railway track system.
-
B.
trackGaugeUnit
Indicates the unit of measurement used to express the gauge (width) of a track.
-
C.
formerTrackGauge
Indicates that an entity previously had a specified track gauge, which has since been changed or is no longer in use.
-
D.
trackGaugeOptions
Indicates the available or applicable gauge (measurement) configurations that can be used for a given track.
-
E.
standardGaugeWidthComparison
chosen
Indicates a comparison between the track gauge width of a railway and the standard gauge width to determine if it is equal to, narrower than, or wider than the 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_69eff6ec27b481908c8d7b86c47893d9 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 28, 2026, 12:46 a.m.