Triple
T19972575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swiss locomotive classification |
E480114
|
entity |
| Predicate | letterIndicates |
P87420
|
FINISHED |
| Object | 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: gauge | Statement: [Swiss locomotive classification, letterIndicates, gauge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: letterIndicates Context triple: [Swiss locomotive classification, letterIndicates, gauge]
-
A.
subsequentLettersIndicate
Indicates that the letters immediately following a given position or symbol convey or specify additional information related to that position or symbol.
-
B.
hasLetter
Indicates that one entity contains, includes, or is associated with a specific letter or character.
-
C.
hasLetterBy
Indicates that an entity possesses or is associated with a letter authored or sent by another entity.
-
D.
letter3
Indicates that one entity is the third letter (or character) of another entity, typically a string or word.
-
E.
labelIndication
chosen
Indicates that a label or designation is assigned to an entity to specify its indication, purpose, or intended use.
- 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65bca94c0819095c902a411c4c4b8 |
completed | April 20, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69e537fae79c81909eae39500766d0b6 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.