Triple
T15983289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TGV trainsets |
E387628
|
entity |
| Predicate | recordSpeedContext |
P50982
|
FINISHED |
| Object | world speed record for conventional trains |
—
|
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: world speed record for conventional trains | Statement: [TGV trainsets, recordSpeedContext, world speed record for conventional trains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordSpeedContext Context triple: [TGV trainsets, recordSpeedContext, world speed record for conventional trains]
-
A.
worldSpeedRecordContext
chosen
Indicates the contextual circumstances (such as event, conditions, or category) under which a world speed record is set or recognized.
-
B.
lineSpeedContext
Indicates the contextual conditions or parameters under which a particular line speed is defined, measured, or applied.
-
C.
recordRoute
Indicates that an entity documents or logs the path, sequence, or trajectory taken between locations or states.
-
D.
recordEvent
Indicates that an entity logs or stores information about a specific occurrence or action as an event.
-
E.
soundRecordingSpeed
Indicates the recording speed at which an audio recording was captured or is intended to be played back.
- 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_69d86da94ccc819083d187f5dc6a123e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d9d8e881909b559a3e3ca21d24 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:54 a.m.