Triple
T16598037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ansaldobreda Sirio trams |
E403259
|
entity |
| Predicate | trackGaugeOptions |
P123461
|
FINISHED |
| Object | 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: standard gauge | Statement: [Ansaldobreda Sirio trams, trackGaugeOptions, standard gauge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackGaugeOptions Context triple: [Ansaldobreda Sirio trams, trackGaugeOptions, standard gauge]
-
A.
trackGauge
Indicates the distance between the inner faces of the rails in a railway track system.
-
B.
formerTrackGauge
Indicates that an entity previously had a specified track gauge, which has since been changed or is no longer in use.
-
C.
gaugeType
Indicates the specific kind or category of gauge associated with an entity or measurement.
-
D.
gaugeGroup
Indicates a relationship where a physical or theoretical model is associated with the gauge group that defines its underlying symmetry structure.
-
E.
gaugeServed
Indicates that a gauge or measuring device is currently being supplied or serviced by a particular source or system.
- 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35d7367308190bf57b4a6a7bd33cc |
completed | April 18, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69e296a7d9d0819088555bca6c936e79 |
completed | April 17, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69e2d7fb02f481908885a226c2191231 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:16 a.m.