Triple
T25032633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cannonvale |
E626888
|
entity |
| Predicate | marineProximity |
P117087
|
FINISHED |
| Object | Great Barrier Reef |
—
|
NE NERFINISHED |
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: Great Barrier Reef | Statement: [Cannonvale, marineProximity, Great Barrier Reef]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marineProximity Context triple: [Cannonvale, marineProximity, Great Barrier Reef]
-
A.
hasNearbyMarineFeature
chosen
Indicates that one entity is located close to a marine geographic feature associated with the other entity.
-
B.
marineArea
Indicates a relationship where an entity is located in, associated with, or relevant to a specific marine or oceanic area.
-
C.
stateOnNearestShore
Indicates that an entity is located on the shore that is geographically closest to another specified reference point or entity.
-
D.
marineResources
Indicates a relationship where one entity possesses, provides, or is associated with marine-based resources (such as fish, minerals, or other ocean-derived materials) used or managed by another entity.
-
E.
visibilityFromShore
Indicates that something can be seen or is visually detectable from the shoreline or coast.
- 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_69e2ff2a2c088190be513727ee8bfe78 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
Created at: April 18, 2026, 6:07 a.m.