Triple
T14494385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Island |
E359452
|
entity |
| Predicate | hasCoastGuardPresence |
P58077
|
FINISHED |
| Object | periodic patrols |
—
|
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: periodic patrols | Statement: [East Island, hasCoastGuardPresence, periodic patrols]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoastGuardPresence Context triple: [East Island, hasCoastGuardPresence, periodic patrols]
-
A.
hasCoastGuard
chosen
Indicates that an entity possesses, is served by, or is under the jurisdiction of a coast guard organization.
-
B.
coastGuardType
Indicates that one entity is classified as a specific type or category within a coast guard organization.
-
C.
coastGuardSector
Indicates that one entity is the U.S. Coast Guard sector responsible for overseeing or serving the other entity.
-
D.
hasCoastlineDesignation
Indicates that a geographic area’s coastline has been assigned a specific official classification or status.
-
E.
hasCoastalSection
Indicates that a geographic entity includes at least one section of land that directly borders a sea or ocean.
- 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de930f34d08190b4b30e54e2f702ed |
completed | April 14, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69de5c4ccba08190a988bfda0bc9f5cb |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:21 a.m.