Triple
T38577957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sportsman’s Park |
E929457
|
entity |
| Predicate | isCoastalTownParkOf |
P56288
|
FINISHED |
| Object | Lantana, Florida |
—
|
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: Lantana, Florida | Statement: [Sportsman’s Park, isCoastalTownParkOf, Lantana, Florida]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCoastalTownParkOf Context triple: [Sportsman’s Park, isCoastalTownParkOf, Lantana, Florida]
-
A.
isCoastalPark
chosen
Indicates that a park is located along or directly adjacent to a coastline.
-
B.
isCoastalDestinationFor
Indicates that a place serves as a seaside or ocean-adjacent travel destination for a particular person, group, or market.
-
C.
isCoastalSettlementOf
Indicates that a settlement is located on or near the coast within the territory of a specified geographic or administrative area.
-
D.
isCoastalLocality
Indicates that a locality is situated on or directly adjacent to a sea, ocean, or significant coastal body of water.
-
E.
isCoastalLandmarkOf
Indicates that a landmark is located on or very near the coast of a specified geographic area or body of water.
- 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_69f76ebd2248819083978362d81fa35e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.