Triple
T38522403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keyes Pond |
E922520
|
entity |
| Predicate | hasRecreationalCharacter |
P112901
|
FINISHED |
| Object | low-intensity use |
—
|
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: low-intensity use | Statement: [Keyes Pond, hasRecreationalCharacter, low-intensity use]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecreationalCharacter Context triple: [Keyes Pond, hasRecreationalCharacter, low-intensity use]
-
A.
hasRecreationalAspect
chosen
Indicates that something includes, involves, or is characterized by a recreational or leisure-related component or purpose.
-
B.
hasRecreationalContext
Indicates that something occurs, is used, or is understood within a leisure, entertainment, or recreational setting or purpose.
-
C.
isRecreational
Indicates that something is used or intended primarily for leisure, enjoyment, or non-work-related activities.
-
D.
hasRecreationPurpose
Indicates that something is used or intended to be used for recreational or leisure activities.
-
E.
hasRecreationalArea
Indicates that an entity includes, provides, or is associated with a designated space intended for leisure or recreational activities.
- 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_69f76ea5f5588190bd0b28c82e975640 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.