Triple
T36194584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R188 |
E1047086
|
entity |
| Predicate | CBTCCompatible |
P55995
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [R188, CBTCCompatible, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CBTCCompatible Context triple: [R188, CBTCCompatible, true]
-
A.
hasAutomaticTrainControlCompatibility
chosen
Indicates that an entity is compatible with, or supports integration with, an automatic train control (ATC) system.
-
B.
usesRollingStockCompatibleWith
Indicates that one entity operates using rolling stock that is technically and operationally compatible with the rolling stock standards or systems associated with another entity.
-
C.
hasSoftwareCompatibilityWith
Indicates that one software system can operate correctly and effectively with another software system, without conflicts or required modifications.
-
D.
hasAutomaticTrainControl
Indicates that an entity is equipped with or uses an automatic train control system for managing train operations.
-
E.
hasFareControlIntegrationSince
Indicates that a fare control system has been integrated with another system or entity starting from a specific point in time.
- 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_69f76e3d4fbc81908c159c7beeb4ce00 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.