Triple
T15651096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Firiplaka |
E376312
|
entity |
| Predicate | hasSeaBottomType |
P4263
|
FINISHED |
| Object | sandy with some rocks |
—
|
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: sandy with some rocks | Statement: [Firiplaka, hasSeaBottomType, sandy with some rocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeaBottomType Context triple: [Firiplaka, hasSeaBottomType, sandy with some rocks]
-
A.
seafloorType
chosen
Indicates the classification of the ocean bottom surface based on its physical or geological characteristics.
-
B.
isShallowSea
Indicates that a body of water is a shallow marine area, typically near coasts or continental shelves, rather than deep ocean.
-
C.
hasBottomWater
Indicates that an entity contains or is associated with water specifically located at its bottom or lowest part.
-
D.
hasOceanType
Indicates that a body of water is classified as belonging to a particular type of ocean or oceanic category.
-
E.
hasSeaArmType
Indicates that an entity is associated with or characterized by a specific type of sea arm (such as a bay, gulf, fjord, or similar marine inlet).
- 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_69d85cd1564c8190991adda63bfab4b0 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04eeed2d48190a7a8a618d90012d0 |
completed | April 16, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69deda890140819082608931e993dd61 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:15 a.m.