Triple
T8177184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ITX-Saemaeul |
E190965
|
entity |
| Predicate | relativeSpeedComparedToConventionalTrains |
P81274
|
FINISHED |
| Object | faster |
—
|
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: faster | Statement: [ITX-Saemaeul, relativeSpeedComparedToConventionalTrains, faster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeSpeedComparedToConventionalTrains Context triple: [ITX-Saemaeul, relativeSpeedComparedToConventionalTrains, faster]
-
A.
hasHighSpeedLine
Indicates that there exists a high-speed rail line connection between the related entities.
-
B.
trainTypeUsed
Indicates that a specific type or category of train is employed or operated in a given context or service.
-
C.
trains
Indicates that one entity teaches, instructs, or coaches another entity to develop skills, knowledge, or abilities.
-
D.
hasUndergroundHighSpeedPlatforms
Indicates that an entity is equipped with high-speed transportation platforms located underground.
-
E.
vehiclesPerTrain
Indicates the number of vehicles that are attached to or make up a single train.
- 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_69ca82c1c0a08190bf8692b4d91a03ca |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4aba0dd88190828080d0d89612eb |
completed | March 31, 2026, 4:16 a.m. |
| PD | Predicate disambiguation | batch_69cb36a7952481908f34e3e82f375a84 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb45503eec8190aeef0da6c3324710 |
completed | March 31, 2026, 3:53 a.m. |
Created at: March 30, 2026, 5:40 p.m.