Triple
T37415454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coalhouse Point |
E929692
|
entity |
| Predicate | hasCoastalDefenseRole |
P45947
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Coalhouse Point, hasCoastalDefenseRole, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoastalDefenseRole Context triple: [Coalhouse Point, hasCoastalDefenseRole, yes]
-
A.
coastalDefense
chosen
Indicates a defensive relationship in which structures, systems, or actions are used to protect a coastline or shore area from threats such as erosion, flooding, or attack.
-
B.
hasCoastalDistrict
Indicates that an administrative region or area includes at least one district that borders a sea or ocean.
-
C.
hasNavalPresenceIn
Indicates that an entity maintains or deploys naval forces or maritime assets within a specified geographic area or location.
-
D.
hasCoastalRegion
Indicates that a place possesses at least one region that borders or is directly adjacent to a sea or ocean.
-
E.
hasCoastGuard
Indicates that an entity possesses, is served by, or is under the jurisdiction of a coast guard organization.
- 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_69f76ebde49481908566cd96b37ccc84 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.