Triple
T28536191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Duck Key |
E722169
|
entity |
| Predicate | positionRelativeToSevenMileBridge |
P133549
|
FINISHED |
| Object | western end |
—
|
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: western end | Statement: [Little Duck Key, positionRelativeToSevenMileBridge, western end]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionRelativeToSevenMileBridge Context triple: [Little Duck Key, positionRelativeToSevenMileBridge, western end]
-
A.
riverMilepost
Indicates the specific distance or position along a river, measured in miles from a defined starting point.
-
B.
positionRelativeToBridge
chosen
Indicates the spatial position of an entity in relation to a specific bridge, such as being on, under, near, or adjacent to it.
-
C.
approximateMileMarker
Indicates an estimated or not precisely measured position along a route expressed in miles.
-
D.
positionRelativeToCoast
Indicates the spatial relationship of something to a coastline, such as its distance or orientation relative to the coast.
-
E.
positionRelativeToTown
Indicates the spatial position or orientation of one place or object in relation to a specified town.
- 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: April 28, 2026, 3:32 a.m.