Triple
T21433887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort National |
E528756
|
entity |
| Predicate | accessibleAtLowTide |
P118906
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Fort National, accessibleAtLowTide, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessibleAtLowTide Context triple: [Fort National, accessibleAtLowTide, yes]
-
A.
visibleWhenWaterLow
Indicates that something becomes visible or can be seen when the water level is low.
-
B.
atEbbTide
chosen
Indicates that the related event or state occurs when the tide is at its lowest level (ebb tide).
-
C.
positionRelativeToTide
Indicates the spatial relationship of something’s location with respect to the current or expected tide level or tidal zone.
-
D.
touchesSea
Indicates that one entity is in direct physical contact with the sea or coastline of another entity.
-
E.
hasTidalRange
Indicates the relationship between a location or body of water and the magnitude of difference between its high and low tide levels.
- 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_69e0c4569fa081908101baa24f8745db |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b5344c048190adfa6f6dd1b453ac |
completed | April 22, 2026, 11:47 a.m. |
| PD | Predicate disambiguation | batch_69e61639ee288190889ffd500d1260f6 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 6 p.m.