Triple
T6863608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sandringham line |
E158340
|
entity |
| Predicate | freightUse |
P28699
|
FINISHED |
| Object | minimal |
—
|
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: minimal | Statement: [Sandringham line, freightUse, minimal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: freightUse Context triple: [Sandringham line, freightUse, minimal]
-
A.
isOnFreightRoute
Indicates that something lies along or is included within a designated freight transportation route used for moving goods.
-
B.
logisticsFeature
chosen
Indicates that something possesses a characteristic, capability, or function specifically related to logistics operations or processes.
-
C.
freightTraffic
Indicates the movement or volume of goods and cargo being transported, typically via commercial transport networks such as rail, road, sea, or air.
-
D.
usesSharedFreightTracks
Indicates that two or more entities operate their freight services on the same railway tracks or infrastructure.
-
E.
usesTransport
Indicates that an entity employs or relies on a particular mode or means of transportation to move from one place to another.
- 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_69c68830cdbc8190a8301c7a9d9f651a |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6da3ce95081909a424ac04bc7fa07 |
completed | March 27, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b168908190b2f7c724b1bc7fc9 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:21 p.m.