Triple
T4966844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galápagos Marine Reserve |
E111548
|
entity |
| Predicate | managementPlan |
P8851
|
FINISHED |
| Object | zoning scheme for different uses and protection levels |
—
|
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: zoning scheme for different uses and protection levels | Statement: [Galápagos Marine Reserve, managementPlan, zoning scheme for different uses and protection levels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managementPlan Context triple: [Galápagos Marine Reserve, managementPlan, zoning scheme for different uses and protection levels]
-
A.
hasManagementPlan
chosen
Indicates that an entity is associated with a defined management plan specifying how it should be overseen, maintained, or administered.
-
B.
planningDocument
Indicates that an entity serves as or is associated with a document created for planning or outlining future actions, strategies, or activities.
-
C.
managementApproach
Indicates the strategy, methods, or style used to direct, organize, and oversee the activities or resources of an entity or process.
-
D.
plan
Indicates that an entity intends or arranges for a future action or sequence of actions to occur.
-
E.
plannedUnder
Indicates that one entity has been scheduled, organized, or arranged to occur within the scope, authority, or framework of another entity.
- 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_69bd4419393c819086319a6fe4bf8542 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd72e49b048190bac55d9e7a6f7963 |
completed | March 20, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_69bd71447fe88190bb62c5e8753da7a7 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:32 p.m.