Triple
T31587998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Manatee State Park |
E806005
|
entity |
| Predicate | hasCampingAmenity |
P197452
|
FINISHED |
| Object | electric hookups |
—
|
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: electric hookups | Statement: [Lake Manatee State Park, hasCampingAmenity, electric hookups]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCampingAmenity Context triple: [Lake Manatee State Park, hasCampingAmenity, electric hookups]
-
A.
hasCampingOption
Indicates that an entity offers or includes the possibility to camp (e.g., designated camping facilities or areas).
-
B.
hasCampingStyle
Indicates that an entity is associated with a particular style or manner of camping.
-
C.
hasCampingTable
Indicates that one entity possesses or includes a camping table as part of its equipment or contents.
-
D.
hasCampingPolicy
Indicates that an entity specifies rules, restrictions, or guidelines regarding camping activities on its premises or within its jurisdiction.
-
E.
roleIn"Camping"
Indicates that an entity has a specific role or function within the context of camping.
- F. None of above. chosen
Provenance (4 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe920a437081908d5174e8cf7a53a6 |
completed | May 9, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69fe919a9a6c8190acb4483f386e6db7 |
completed | May 9, 2026, 1:44 a.m. |
| PDg | Predicate description generation | batch_69fe9208ed708190980fb5061b22ae49 |
completed | May 9, 2026, 1:46 a.m. |
Created at: April 30, 2026, 10:26 p.m.