Triple
T6487574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ustica |
E146551
|
entity |
| Predicate | hasMarineReserveStatus |
P56408
|
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: [Ustica, hasMarineReserveStatus, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMarineReserveStatus Context triple: [Ustica, hasMarineReserveStatus, yes]
-
A.
hasMarineReserve
chosen
Indicates that an entity possesses, includes, or is associated with a designated marine reserve area.
-
B.
marineProtectedAreaOf
Indicates that one entity is designated as a marine protected area that encompasses, is associated with, or provides protection for the other entity.
-
C.
marineProtectedArea
Indicates that an area of marine or coastal waters is designated and managed to conserve natural resources and biodiversity, often restricting certain human activities.
-
D.
hasMarineManagement
Indicates that an entity exercises authority or responsibility over the planning, regulation, or stewardship of marine areas or resources.
-
E.
marineProtectedAreaManagingCountry
Indicates that a country is responsible for managing or overseeing a specific marine protected area.
- 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_69c0090158c08190af0df9a2348d2d52 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06a96a4048190a28dee5fd9258486 |
completed | March 22, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69c06740bebc81909d9d6956baa2bcb9 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:52 p.m.