Triple
T37725051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anacostia Rail Holdings |
E939693
|
entity |
| Predicate | transportedGoodsType |
P199174
|
FINISHED |
| Object | bulk commodities |
—
|
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 commodities | Statement: [Anacostia Rail Holdings, transportedGoodsType, bulk commodities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportedGoodsType Context triple: [Anacostia Rail Holdings, transportedGoodsType, bulk commodities]
-
A.
transportedWith
Indicates that one entity was moved or carried together with another entity as part of the same transport event.
-
B.
transportedAs
Indicates that one entity is moved or carried from one place to another in the form, role, or medium specified by another entity.
-
C.
commonlyTransportedIn
Indicates that something is usually carried, moved, or conveyed using a particular vehicle, container, or mode of transport.
-
D.
typeOfHaulage
Indicates the kind or category of haulage service or transport operation associated with an entity.
-
E.
hasTransportCommodity
chosen
Indicates that a mode of transport carries or is used to move a specified commodity or type of goods.
- 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_69f76edc208c8190bc8b9683f75e1024 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffc605b0648190a7abe9128b0d857a |
completed | May 9, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69ffc5742d80819099f947ece78d5700 |
completed | May 9, 2026, 11:38 p.m. |
Created at: May 3, 2026, 4:18 p.m.