Triple
T21538844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nash Sands islets |
E531422
|
entity |
| Predicate | maritimeStatus |
P70147
|
FINISHED |
| Object | navigation hazard |
—
|
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: navigation hazard | Statement: [Nash Sands islets, maritimeStatus, navigation hazard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maritimeStatus Context triple: [Nash Sands islets, maritimeStatus, navigation hazard]
-
A.
marineProtectionStatus
Indicates the level or type of legal or regulatory protection applied to a marine area or resource.
-
B.
flagStateOfOneVessel
Indicates that one vessel is flying or registered under the national flag (state) of another vessel.
-
C.
maritimeActivity
Indicates activities, operations, or behaviors that take place at sea or are directly related to maritime environments and navigation.
-
D.
sailingStatus
Indicates the current operational state or condition of a vessel in relation to its sailing activity (e.g., underway, docked, anchored, or out of service).
-
E.
hasMarineStatus
chosen
Indicates that an entity possesses a specific classification or condition related to its status in a marine or oceanic 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_69e0c45f17148190949c330ab9c27706 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee9d10a2888190bc4e502a829c76a4 |
completed | April 26, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69e6320766308190ba5dca2f7c826aa4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:27 p.m.