Triple
T3549840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yasawa Islands |
E75083
|
entity |
| Predicate | hasMarineFeature |
P11765
|
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: [Yasawa Islands, hasMarineFeature, coral reefs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMarineFeature Context triple: [Yasawa Islands, hasMarineFeature, coral reefs]
-
A.
hasMarineEcosystem
chosen
Indicates that an entity possesses, contains, or is associated with a marine ecosystem as part of its characteristics or environment.
-
B.
hasShoreFeature
Indicates that a shore or coastline possesses a specific physical or environmental feature.
-
C.
hasMarineSpecies
Indicates that an entity contains, supports, or is associated with one or more marine species.
-
D.
hasMarineResource
Indicates that one entity possesses, contains, or is associated with a marine (ocean or sea-based) resource in relation to another entity.
-
E.
containsCoastalFeature
Indicates that one entity geographically includes or encompasses a coastal feature (such as a beach, cliff, bay, or shoreline) within its area or boundaries.
- 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_69ad85d33c6c819081d5ac1df13b5680 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbfd38c8c8190a4591689ad57c998 |
completed | March 8, 2026, 6:28 p.m. |
| PD | Predicate disambiguation | batch_69adb83270ac819083967db0570167d2 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:20 p.m.