Triple
T22268232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbia Reef |
E550405
|
entity |
| Predicate | hasDiveCondition |
P147611
|
FINISHED |
| Object | moderate current |
—
|
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: moderate current | Statement: [Columbia Reef, hasDiveCondition, moderate current]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDiveCondition Context triple: [Columbia Reef, hasDiveCondition, moderate current]
-
A.
hasDivingComponent
Indicates that an activity, event, or process includes or involves a diving-related element or action.
-
B.
hasDiveType
Indicates that an entity performs or is associated with a specific type or category of dive.
-
C.
hasDiveDifficulty
Indicates that an action or event of diving is associated with a specified level of difficulty.
-
D.
hasDivingDepth
Indicates that an entity is associated with a specific depth to which it can or does dive.
-
E.
hasDiveLoop
Indicates that an entity (typically a roller coaster) includes a dive loop inversion element in its layout.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e7342ce08c8190bc0a7085f4a952e7 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:39 p.m.