Triple
T32506859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CZ 97B |
E830821
|
entity |
| Predicate | hasAccessoryRail |
P181271
|
FINISHED |
| Object | no (on early standard models) |
—
|
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: no (on early standard models) | Statement: [CZ 97B, hasAccessoryRail, no (on early standard models)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccessoryRail Context triple: [CZ 97B, hasAccessoryRail, no (on early standard models)]
-
A.
hasRail
Indicates that something is equipped with, includes, or is connected to a rail or rail system.
-
B.
hasRackRailway
Indicates that one entity possesses or includes a rack railway system connecting locations or operating within its area.
-
C.
hasRailMode
Indicates that an entity is associated with or supports transportation via rail-based modes (such as trains, trams, or subways).
-
D.
hasRailDeck
Indicates that something is equipped with or includes a deck specifically designed for carrying rail vehicles or tracks.
-
E.
hasRailWidth
Indicates that one entity has a specified width measurement for its rail or rails.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f76759b3c48190ad8f1b33596f98c4 |
completed | May 3, 2026, 3:18 p.m. |
Created at: May 1, 2026, 1 a.m.