Triple
T26906220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Star Line |
E677261
|
entity |
| Predicate | secondaryCargo |
P180398
|
FINISHED |
| Object | general freight |
—
|
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 freight | Statement: [Red Star Line, secondaryCargo, general freight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryCargo Context triple: [Red Star Line, secondaryCargo, general freight]
-
A.
secondaryPayload
Indicates that an entity serves as an additional or subordinate payload associated with a primary payload in an action or relationship.
-
B.
secondaryProducts
Indicates that certain entities arise as secondary or byproduct outputs from a primary process, activity, or production.
-
C.
mainCargo
Indicates that one entity serves as the primary or principal cargo carried or transported by another entity.
-
D.
secondaryTo
Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
-
E.
secondaryArm
Indicates that an entity possesses an additional, non-primary arm used for support, manipulation, or specialized functions.
- 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_69eee9bcef1c8190be88586bb902bb9b |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
| PDg | Predicate description generation | batch_69f74061c440819080434155c2d60341 |
completed | May 3, 2026, 12:32 p.m. |
Created at: April 27, 2026, 5:59 a.m.