Triple
T15670478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint-Brieuc |
E377295
|
entity |
| Predicate | bayProtectedStatus |
P3029
|
FINISHED |
| Object | nature reserve |
—
|
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: nature reserve | Statement: [Saint-Brieuc, bayProtectedStatus, nature reserve]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bayProtectedStatus Context triple: [Saint-Brieuc, bayProtectedStatus, nature reserve]
-
A.
hasProtectedAreaStatus
chosen
Indicates that an area is officially designated and managed as a protected area under relevant conservation or legal frameworks.
-
B.
marineProtectionStatus
Indicates the level or type of legal or regulatory protection applied to a marine area or resource.
-
C.
stateProtectedAreaOf
Indicates that an area is designated and managed as a protected area under the authority of a specific state or subnational government.
-
D.
marineProtectedAreaOf
Indicates that one entity is designated as a marine protected area that encompasses, is associated with, or provides protection for the other entity.
-
E.
countryProtectedAreaStatus
Indicates the legal or administrative protection status that a country assigns to a specific area or region.
- 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_69d85cd2e28481909d4e975bee20872f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04f1254508190a77a16b7bfd299ad |
completed | April 16, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69deda8b36a4819081cb5708fe77ef51 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:16 a.m.