Triple
T35125711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ECO region |
E1014296
|
entity |
| Predicate | includesMaritimeStates |
P131708
|
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: [ECO region, includesMaritimeStates, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesMaritimeStates Context triple: [ECO region, includesMaritimeStates, true]
-
A.
isMaritimeRegion
Indicates that a region is primarily associated with the sea or ocean, such as being coastal, oceanic, or otherwise defined by maritime characteristics or activities.
-
B.
hasMaritimeConnection
Indicates a relationship in which an entity is linked to seas, oceans, or maritime activities, such as shipping, navigation, or coastal operations.
-
C.
nauticalRegion
Indicates that one entity is a maritime or nautical area within which the other entity is located, operates, or is relevant.
-
D.
hasNavalPresenceIn
Indicates that an entity maintains or deploys naval forces or maritime assets within a specified geographic area or location.
-
E.
includesMarineAreas
chosen
Indicates that the referenced spatial or jurisdictional entity encompasses or covers one or more marine or ocean areas within its extent.
- 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_69f76dd8b6948190aaa32b081816bd94 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:02 p.m.