Triple
T3997941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TGV Sud-Est |
E87142
|
entity |
| Predicate | trainsetFormation |
P26476
|
FINISHED |
| Object | 2 power cars and 8 trailers |
—
|
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: 2 power cars and 8 trailers | Statement: [TGV Sud-Est, trainsetFormation, 2 power cars and 8 trailers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trainsetFormation Context triple: [TGV Sud-Est, trainsetFormation, 2 power cars and 8 trailers]
-
A.
typicalFormation
Indicates the usual or characteristic way in which something is formed, structured, or comes into existence.
-
B.
trainConfiguration
chosen
Indicates the specific arrangement and composition of train elements (such as locomotives and cars) used together for a particular operation or service.
-
C.
bandFormation
Indicates the event or process by which a musical band is created or comes together as a group.
-
D.
trainControl
Indicates that one entity exercises authority over or manages the operation, direction, or behavior of another entity in a training or instructional context.
-
E.
tacticalFormation
Indicates a specific strategic arrangement or positioning of entities relative to one another to achieve a tactical objective.
- 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_69aed94118148190975e6aa4e554cde9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefa8579288190940487ad07e38de0 |
completed | March 9, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69aef8f89f2881909b0965419d15d46c |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:34 p.m.