Triple
T4828151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rockpiles surf break |
E107875
|
entity |
| Predicate | hasBottomType |
P55347
|
FINISHED |
| Object | reef |
—
|
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: reef | Statement: [Rockpiles surf break, hasBottomType, reef]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBottomType Context triple: [Rockpiles surf break, hasBottomType, reef]
-
A.
hasBottomSubstrate
chosen
Indicates that one entity serves as the underlying or supporting substrate or base layer for another entity.
-
B.
bottomType
Indicates that the subject entity is classified as a bottom-level or most specific type within a type hierarchy.
-
C.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
D.
hasBottomWater
Indicates that an entity contains or is associated with water specifically located at its bottom or lowest part.
-
E.
hasFlowType
Indicates the type or category of flow associated with or exhibited by an 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_69bd43fac8188190803f0327190621e4 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ddd17d881909f7731ff2b460e83 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c1fe130819087ae01309f96a0c8 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:24 p.m.