Triple
T2161111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agadir |
E46802
|
entity |
| Predicate | isCommercialPort |
P36082
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Agadir, isCommercialPort, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCommercialPort Context triple: [Agadir, isCommercialPort, true]
-
A.
isCommercialHubIn
Indicates that a place functions as a primary center of commercial or business activity within a specified larger area or region.
-
B.
hasCommercialFunction
Indicates that an entity serves a commercial role or purpose, such as engaging in trade, sales, or other profit-oriented activities.
-
C.
isInlandPort
Indicates that a port facility is located inland, away from the open sea, typically on a river, canal, or lake, while still serving maritime or shipping functions.
-
D.
isDeepWaterPort
Indicates that a port has sufficiently deep water to accommodate large, heavily loaded vessels without grounding.
-
E.
isCommercialArmOf
Indicates that one entity functions as the business or revenue-generating division, subsidiary, or operational branch of another entity.
- 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_69a88a184cbc8190877791f6552c2484 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbe89e6ac8190b4b4bc0be4fe7aa9 |
completed | March 7, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69abbd9c90408190b6b65498ca43ce26 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbe1ecb7081909c2c66da08a48ab7 |
completed | March 7, 2026, 5:56 a.m. |
Created at: March 4, 2026, 7:45 p.m.