Triple
T19972551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UIC classification |
E480113
|
entity |
| Predicate | hasNotationRule |
P95660
|
FINISHED |
| Object | capital letters indicate powered axle groups |
—
|
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: capital letters indicate powered axle groups | Statement: [UIC classification, hasNotationRule, capital letters indicate powered axle groups]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotationRule Context triple: [UIC classification, hasNotationRule, capital letters indicate powered axle groups]
-
A.
usesNotationFor
chosen
Indicates that one entity employs or adopts a particular notation system or symbolic representation for another entity.
-
B.
hasRule
Indicates that an entity is governed, constrained, or defined by a specific rule or set of rules.
-
C.
hasRangeNotation
Indicates that a value, property, or parameter is expressed using a range-style notation (e.g., lower and upper bounds) rather than as a single discrete value.
-
D.
hasRuleFor
Indicates that one entity defines or applies a rule that governs or constrains another entity or situation.
-
E.
hasObjectNotation
Indicates that an entity is represented or expressed using a specific object-based notation or symbolic format.
- 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.