Triple
T32457066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ko Tub |
E829456
|
entity |
| Predicate | connectedToAtLowTide |
P174091
|
FINISHED |
| Object | Ko Kai |
—
|
NE NERFINISHED |
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: Ko Kai | Statement: [Ko Tub, connectedToAtLowTide, Ko Kai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedToAtLowTide Context triple: [Ko Tub, connectedToAtLowTide, Ko Kai]
-
A.
atEbbTide
Indicates that the related event or state occurs when the tide is at its lowest level (ebb tide).
-
B.
visibleWhenWaterLow
Indicates that something becomes visible or can be seen when the water level is low.
-
C.
hasTidalConnection
Indicates that one entity is linked to another through the movement, influence, or exchange of tidal waters.
-
D.
tideDependentAccess
chosen
Indicates that access between locations or to a place is only possible or practical under certain tidal conditions.
-
E.
receivesTideFrom
Indicates that one entity obtains or is affected by tidal influence originating from 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_69f3491df9288190afc0b23b1d6e72ce |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fecb4d02f881909a9ee97ce98000d5 |
completed | May 9, 2026, 5:51 a.m. |
| PD | Predicate disambiguation | batch_69fec9846c1c8190b317f0711f0755db |
completed | May 9, 2026, 5:43 a.m. |
Created at: May 1, 2026, 12:56 a.m.