Triple
T19469117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BCDC |
E487076
|
entity |
| Predicate | hasMainRegulatoryArea |
P46644
|
FINISHED |
| Object | coastal zone management |
—
|
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: coastal zone management | Statement: [BCDC, hasMainRegulatoryArea, coastal zone management]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainRegulatoryArea Context triple: [BCDC, hasMainRegulatoryArea, coastal zone management]
-
A.
hasPrimaryServiceArea
chosen
Indicates that an entity is associated with a main geographic or functional area in which it primarily provides its services.
-
B.
hasAdministrativeArea
Indicates that one entity serves as the governing or jurisdictional area responsible for administering another entity.
-
C.
hasRegulatedBy
Indicates that one entity is subject to control, governance, or rules imposed by another entity.
-
D.
hasRegulatoryMarket
Indicates that an entity is subject to, or operates within, a specific regulatory framework or market oversight regime.
-
E.
hasMainGoverningBody
Indicates that an entity possesses a primary official organization or authority responsible for its overall governance or decision-making.
- 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633e6fd988190b79be580b65746fe |
completed | April 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7499a4819082bec0be8afba35c |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:39 p.m.