Triple
T4181336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belize Barrier Reef Reserve System |
E88200
|
entity |
| Predicate | hasMainEconomicUse |
P54269
|
FINISHED |
| Object | tourism |
—
|
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: tourism | Statement: [Belize Barrier Reef Reserve System, hasMainEconomicUse, tourism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainEconomicUse Context triple: [Belize Barrier Reef Reserve System, hasMainEconomicUse, tourism]
-
A.
hasEconomicImportanceFor
Indicates that one entity holds economic value, benefit, or significance for another entity.
-
B.
majorLandUse
Indicates the primary way a given area of land is utilized or designated (e.g., residential, commercial, agricultural).
-
C.
primaryLandUse
Indicates the main or dominant way in which a given piece of land is utilized or designated (e.g., residential, agricultural, commercial).
-
D.
hasIndustrialSignificance
Indicates that something plays an important role or has notable impact within industrial processes, production, or applications.
-
E.
hasWatershedUse
Indicates that a particular type of use, activity, or function is associated with or applied to a watershed.
- F. None of above. chosen
Provenance (4 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_69aed9477e8c81908bcb862d2db55b1d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af07078cb081909f64326b12522410 |
completed | March 9, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69af019155448190b19868583272513f |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af07059d288190a1ea79449414fbce |
completed | March 9, 2026, 5:44 p.m. |
Created at: March 9, 2026, 3:45 p.m.