Triple
T13297670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitung |
E316726
|
entity |
| Predicate | hasMarineEcosystemType |
P108965
|
FINISHED |
| Object | coral reefs |
—
|
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 reefs | Statement: [Bitung, hasMarineEcosystemType, coral reefs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMarineEcosystemType Context triple: [Bitung, hasMarineEcosystemType, coral reefs]
-
A.
hasMarineEcosystem
Indicates that an entity possesses, contains, or is associated with a marine ecosystem as part of its characteristics or environment.
-
B.
hasMarineHabitatType
chosen
Indicates that an entity is associated with or occurs in a specific type of marine habitat.
-
C.
hasMarineEcoregion
Indicates that an entity is associated with, or located within, a specific marine ecoregion.
-
D.
hasMarineSpecies
Indicates that an entity contains, supports, or is associated with one or more marine species.
-
E.
hasAquaticEcosystem
Indicates that an entity possesses, contains, or is associated with an ecosystem primarily based in water (such as rivers, lakes, wetlands, or oceans).
- 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_69d806b40ab4819094adf6c374f4811a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6893708190aeebf4c47386cff7 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:28 p.m.