Triple
T28536223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Duck Key |
E722169
|
entity |
| Predicate | baySide |
P138699
|
FINISHED |
| Object | Gulf side of Florida Keys |
—
|
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: Gulf side of Florida Keys | Statement: [Little Duck Key, baySide, Gulf side of Florida Keys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: baySide Context triple: [Little Duck Key, baySide, Gulf side of Florida Keys]
-
A.
bayView
Indicates that one entity has a view overlooking a bay or is oriented toward a bay.
-
B.
bay
Indicates that one entity howls or barks loudly, often repeatedly, typically in reaction to something such as prey, the moon, or a disturbance.
-
C.
bayLocation
Indicates that an entity (such as a bay) is geographically located in or along a specified place or region.
-
D.
bayAccess
chosen
Indicates that an entity has the ability, right, or means to reach, use, or interact with a specific bay or bay area.
-
E.
bayOf
Indicates that one location is a bay that forms an inlet or coastal indentation associated with another geographic entity, such as a sea, ocean, or coastline.
- 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_69f64fda797081909e259eb25d51e206 |
completed | May 2, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 3:32 a.m.