Triple
T32493628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hudson River |
E830455
|
entity |
| Predicate | isTidalUpTo |
P88668
|
FINISHED |
| Object | Troy |
—
|
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: Troy | Statement: [Hudson River, isTidalUpTo, Troy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTidalUpTo Context triple: [Hudson River, isTidalUpTo, Troy]
-
A.
isTidal
Indicates that something is influenced or driven by tidal forces or tidal movements.
-
B.
isTidalContext
Indicates that the situation or environment is influenced by, related to, or occurring within tidal conditions or tidal cycles.
-
C.
hasTidalConnection
chosen
Indicates that one entity is linked to another through the movement, influence, or exchange of tidal waters.
-
D.
isTidalNear
Indicates that one entity is located close enough to another body of water or coastline to be significantly affected by tidal forces.
-
E.
isOnTidalIsland
Indicates that something is located on a tidal island, i.e., land connected to the mainland at low tide and isolated by water at high tide.
- 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_69f34920aa4081908d8fb0277414b911 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c4087e048190884d3902fdc81aa5 |
completed | May 3, 2026, 3:42 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:59 a.m.