Triple
T34113609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crackling Lake |
E874905
|
entity |
| Predicate | accessRestrictedToBoardwalks |
P181793
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Crackling Lake, accessRestrictedToBoardwalks, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessRestrictedToBoardwalks Context triple: [Crackling Lake, accessRestrictedToBoardwalks, true]
-
A.
hasBoardwalkInfrastructure
Indicates that there exists constructed boardwalk-related facilities or structures associated with the subject.
-
B.
hasOutfieldBoardwalk
Indicates that an outfield area includes or is equipped with a boardwalk structure.
-
C.
isBoardwalkAttraction
Indicates that one entity is an attraction or point of interest located on or directly associated with a boardwalk.
-
D.
boardwalkType
Indicates the specific kind or classification of a boardwalk in relation to its general category or design.
-
E.
accessRestrictedToShore
Indicates that access to something is limited exclusively to locations or entities situated on or near the shore.
- 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_69f349a80d4481908527317d43f5c579 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7824dc3f0819092a5102895b4a478 |
completed | May 3, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
| PDg | Predicate description generation | batch_69f7817c79e081908e685c48165e086b |
completed | May 3, 2026, 5:10 p.m. |
Created at: May 1, 2026, 1:53 a.m.