Triple
T22268221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbia Reef |
E550405
|
entity |
| Predicate | hasTypicalVisibility |
P106282
|
FINISHED |
| Object | high underwater visibility |
—
|
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: high underwater visibility | Statement: [Columbia Reef, hasTypicalVisibility, high underwater visibility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalVisibility Context triple: [Columbia Reef, hasTypicalVisibility, high underwater visibility]
-
A.
hasVisibility
Indicates that one entity can perceive, view, or access another entity or its information under certain conditions.
-
B.
typicalVisibility
chosen
Indicates the usual or expected degree to which one entity can be seen or perceived from another under normal conditions.
-
C.
hasVisibilityCharacteristic
Indicates that one entity possesses a specific property or quality related to how visible or observable it is.
-
D.
hasTypicalAccess
Indicates that one entity normally or customarily has the ability, permission, or means to access or use another entity.
-
E.
isPartiallyVisibleFrom
Indicates that one entity can be seen only in part, rather than fully, from the viewpoint or location of another entity.
- 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_69e11e43d8208190aff4f9cf7f2c2a8a |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f141bd0ea88190b3574883b695d56c |
completed | April 28, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:39 p.m.