Triple
T26440833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lloyd Triestino |
E665080
|
entity |
| Predicate | hasTransported |
P181203
|
FINISHED |
| Object | general cargo |
—
|
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: general cargo | Statement: [Lloyd Triestino, hasTransported, general cargo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTransported Context triple: [Lloyd Triestino, hasTransported, general cargo]
-
A.
transportedAfter
Indicates that one entity is transported only after the transportation of another entity has occurred in time.
-
B.
transportedWith
Indicates that one entity was moved or carried together with another entity as part of the same transport event.
-
C.
transportedFor
Indicates that one entity was moved or carried from one place to another for the benefit, use, or purpose of another entity or activity.
-
D.
transportedOver
Indicates that something is moved or carried across or along a specified medium, route, or surface.
-
E.
hasTransportationAbove
Indicates that one entity provides or has transportation infrastructure or services located above another entity (e.g., elevated roads, railways, or transit lines).
- 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_69ee883c851881909e2ab04efbb3c5fe |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f76759b3c48190ad8f1b33596f98c4 |
completed | May 3, 2026, 3:18 p.m. |
Created at: April 26, 2026, 11:58 p.m.