Triple
T30219752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yurigahama sandbar |
E768309
|
entity |
| Predicate | emerges |
P101679
|
FINISHED |
| Object | at low tide |
—
|
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: at low tide | Statement: [Yurigahama sandbar, emerges, at low tide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emerges Context triple: [Yurigahama sandbar, emerges, at low tide]
-
A.
emergesAs
Indicates that one entity comes to be recognized, develops, or appears in the role, form, or status of another entity over time.
-
B.
emergedFrom
Indicates that one entity originated, arose, or came forth from another entity or source.
-
C.
emergedWith
Indicates that one entity came forth, appeared, or became visible at the same time and in association with another entity.
-
D.
emergesAt
chosen
Indicates that something comes into existence, becomes visible, or starts to be apparent at a specific time, place, or condition.
-
E.
reemergesAs
Indicates that an entity that previously disappeared, transformed, or became inactive later appears again in a new or altered form.
- 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_69f2247fd8b8819087fcf83cb7a05eb8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ff8bc9081909ad67eeac8291bf6 |
completed | May 2, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:34 p.m.