Triple
T28173865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North America and Africa |
E715534
|
entity |
| Predicate | keyRegionsFor |
P10082
|
FINISHED |
| Object | North Atlantic 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: North Atlantic shipping | Statement: [North America and Africa, keyRegionsFor, North Atlantic shipping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyRegionsFor Context triple: [North America and Africa, keyRegionsFor, North Atlantic shipping]
-
A.
isKeyRegionFor
chosen
Indicates that one region plays a central or strategically important role in relation to a specified process, function, or larger area.
-
B.
coreRegionOf
Indicates that one entity constitutes the central or most essential part of another entity’s structure, area, or domain.
-
C.
includedRegions
Indicates that certain regions are contained within, or form part of, a larger specified region or set of regions.
-
D.
exportRegion
Indicates the region or geographic area from which goods, services, or resources are exported.
-
E.
isKeyRegionIn
Indicates that a region plays a central or strategically important role within a larger area, system, or context.
- 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_69efd6b340f0819095680e15dcdc1830 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6423853ec8190892ecc3e097deeb3 |
completed | May 2, 2026, 6:28 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 10:14 p.m.