Triple
T30848381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SNCF Class B 83500 |
E785706
|
entity |
| Predicate | electricOperation |
P61173
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [SNCF Class B 83500, electricOperation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electricOperation Context triple: [SNCF Class B 83500, electricOperation, yes]
-
A.
usesElectricityFor
chosen
Indicates that one entity relies on or employs electricity as the power source to operate, perform a function, or carry out an activity for another entity or purpose.
-
B.
electricalPower
Indicates that one entity supplies, carries, or is associated with electrical power to or for another entity.
-
C.
usesElectricityStandard
Indicates that one entity operates according to, or is compatible with, the electricity supply standard defined or used by another entity.
-
D.
typicalEquipmentPowered
Indicates that one entity is commonly powered or operated by another entity as its usual source of power.
-
E.
isElectrically
Indicates that one entity has an electrical property, connection, or interaction in relation to another entity.
- 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_69f224b850848190a4af4ccf8ddadcdf |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe12a899d4819080d48423f32eace9 |
completed | May 8, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69fe0d7f6aa08190a1d2dfc025d4e0dc |
completed | May 8, 2026, 4:21 p.m. |
Created at: April 29, 2026, 8:46 p.m.