Triple
T37853646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Astatula, Florida |
E944122
|
entity |
| Predicate | waterRecreationAccess |
P8966
|
FINISHED |
| Object | boating |
—
|
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: boating | Statement: [Astatula, Florida, waterRecreationAccess, boating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterRecreationAccess Context triple: [Astatula, Florida, waterRecreationAccess, boating]
-
A.
waterwayAccess
Indicates that one location has direct access to a waterway (such as a river, canal, or sea route) that can be used for transport, navigation, or related activities.
-
B.
recreationAccess
chosen
Indicates that one entity provides or has the ability to use recreational facilities, activities, or spaces associated with another entity.
-
C.
hasFishingAccess
Indicates that an entity is permitted or able to fish in or otherwise use a particular water body or fishing area.
-
D.
hasWaterfrontAccessTo
Indicates that one entity is directly adjacent to and can physically access a particular body of water, such as a lake, river, or ocean.
-
E.
hasBoatRamp
Indicates that a location provides a designated ramp or launch area for putting boats into the water or taking them out.
- 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_69f76eed4d9c81908b1b71ba9e3b61fe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe6fea4a288190bf8615c5d6bf41b4 |
completed | May 8, 2026, 11:21 p.m. |
| PD | Predicate disambiguation | batch_69fe6f774de08190975a2393b9a1fd22 |
completed | May 8, 2026, 11:19 p.m. |
Created at: May 3, 2026, 4:19 p.m.