Triple
T32880596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SNCF Fret |
E841051
|
entity |
| Predicate | hasTransportCommodity |
P199174
|
FINISHED |
| Object | bulk goods |
—
|
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: bulk goods | Statement: [SNCF Fret, hasTransportCommodity, bulk goods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTransportCommodity Context triple: [SNCF Fret, hasTransportCommodity, bulk goods]
-
A.
hasTransporters
Indicates that one entity possesses, provides, or is equipped with one or more means of transportation for another entity or purpose.
-
B.
hasTransportCategory
Indicates that one entity is classified under a particular category or type of transport associated with another entity.
-
C.
hasTransportCode
Indicates that an entity is associated with a specific transport-related code used to identify or classify its mode, method, or details of transportation.
-
D.
isTransport
Indicates that one entity serves as a means or method for conveying or carrying another entity from one place to another.
-
E.
transportedWith
Indicates that one entity was moved or carried together with another entity as part of the same transport event.
- 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_69f349446e288190a70c05bcc4d81172 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff246e0d4481908bcec718e1d4025b |
completed | May 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69ff23cb70ac81909b776ace4597ae9c |
completed | May 9, 2026, 12:08 p.m. |
| PDg | Predicate description generation | batch_69ff246d53cc81909d5528224149b04b |
completed | May 9, 2026, 12:11 p.m. |
Created at: May 1, 2026, 1:18 a.m.