Triple
T27775235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horse Caves (Mount Norwottuck) |
E699165
|
entity |
| Predicate | isRecreationalSite |
P56580
|
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: [Horse Caves (Mount Norwottuck), isRecreationalSite, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRecreationalSite Context triple: [Horse Caves (Mount Norwottuck), isRecreationalSite, true]
-
A.
isRecreationalArea
chosen
Indicates that a place or space is designated and used primarily for leisure, relaxation, or recreational activities.
-
B.
isRecreationalFacility
Indicates that the subject entity functions as a place or installation intended for leisure, sports, or other recreational activities.
-
C.
hasRecreationalAspect
Indicates that something includes, involves, or is characterized by a recreational or leisure-related component or purpose.
-
D.
hasRecreationalArea
Indicates that an entity includes, provides, or is associated with a designated space intended for leisure or recreational activities.
-
E.
isRecreationalGateway
Indicates that something serves as an entry point or access hub for recreational activities or leisure experiences.
- 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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63894e5848190aec428392562ab06 |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 5:05 p.m.