Triple
T31429569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marseille metropolitan area |
E801756
|
entity |
| Predicate | hasMajorPortFunction |
P201805
|
FINISHED |
| Object | cargo shipping |
—
|
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: cargo shipping | Statement: [Marseille metropolitan area, hasMajorPortFunction, cargo shipping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorPortFunction Context triple: [Marseille metropolitan area, hasMajorPortFunction, cargo shipping]
-
A.
hasMajorPort
Indicates that a location possesses a primary, significant seaport used for major commercial or transportation activities.
-
B.
hasPortFunctionVia
Indicates that an entity possesses a port or interface that fulfills a specific function by means of, or through, another related element or mechanism.
-
C.
hasMajorComponent
Indicates that one entity includes another entity as a primary or most significant component or part.
-
D.
hasPorts
Indicates that an entity is equipped with or provides access points (ports) for connection, communication, or interface with other entities or systems.
-
E.
hasMajorOutput
Indicates that an entity produces a primary or most significant output, result, or product.
- 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a00233e2170819084bee0c8f74cc1a4 |
completed | May 10, 2026, 6:18 a.m. |
| PD | Predicate disambiguation | batch_6a0022943fd08190b73007f080d5971d |
completed | May 10, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_6a00233d32bc8190bea60b09b46ee7bc |
completed | May 10, 2026, 6:18 a.m. |
Created at: April 30, 2026, 8:56 p.m.