Triple
T7787858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Key Largo, Florida |
E187291
|
entity |
| Predicate | majorEcosystem |
P964
|
FINISHED |
| Object | coral reef ecosystem |
—
|
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: coral reef ecosystem | Statement: [Key Largo, Florida, majorEcosystem, coral reef ecosystem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorEcosystem Context triple: [Key Largo, Florida, majorEcosystem, coral reef ecosystem]
-
A.
primaryEcosystem
chosen
Indicates the main type of ecosystem in which an entity predominantly exists or operates.
-
B.
ecoregion
Indicates that one entity is located within, associated with, or belongs to the same ecological region as another entity.
-
C.
hasMajorEcoregion
Indicates that an entity is primarily located within, or chiefly associated with, a particular major ecological region.
-
D.
partOfEcosystem
Indicates that an entity functions as a component within a larger ecological system, contributing to and affected by its interactions and processes.
-
E.
ecoregionInfluence
Indicates that one ecoregion affects or shapes the environmental characteristics, processes, or conditions of another area or system.
- 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_69ca82af2d2c8190963861f5e0b8bf21 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cae7e779ec8190b77296d9c2ac3210 |
completed | March 30, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69caa488532c819093ac40bba0b3c7ef |
completed | March 30, 2026, 4:27 p.m. |
Created at: March 30, 2026, 4:24 p.m.