Triple
T876876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PTLIS |
E18936
|
entity |
| Predicate | usedInModeOfTransport |
P1379
|
FINISHED |
| Object | maritime transport |
—
|
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: maritime transport | Statement: [PTLIS, usedInModeOfTransport, maritime transport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInModeOfTransport Context triple: [PTLIS, usedInModeOfTransport, maritime transport]
-
A.
usesTransport
Indicates that an entity employs or relies on a particular mode or means of transportation to move from one place to another.
-
B.
transportRole
Indicates that an entity participates in a transportation process with a specific functional role (e.g., carrier, passenger, cargo, or operator).
-
C.
hasPublicTransportUsage
Indicates that an entity makes use of, or is associated with the use of, public transportation services.
-
D.
transportType
chosen
Indicates the mode or means of transportation used in carrying something or someone from one place to another.
-
E.
transportationRole
Indicates a role or function that an entity has specifically in the context of providing, operating, or supporting transportation.
- 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_69a4938db1f081909bcd1ad2713b6096 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4acaf30a48190a10ed7fee464c444 |
completed | March 1, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69a4aa8d47c081909b02a53e305ccf7a |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.