Triple
T35175571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pachaug Pond |
E1015688
|
entity |
| Predicate | recreationPopularity |
P168979
|
FINISHED |
| Object | popular regional destination |
—
|
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: popular regional destination | Statement: [Pachaug Pond, recreationPopularity, popular regional destination]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recreationPopularity Context triple: [Pachaug Pond, recreationPopularity, popular regional destination]
-
A.
recreationalImportance
chosen
Indicates the degree to which something is valued or used for leisure, play, or recreational activities.
-
B.
recreationUseLevel
Indicates the intensity or degree to which an entity is used for recreational activities.
-
C.
recreationLocation
Indicates the place where a recreational activity or leisure pursuit occurs.
-
D.
recreationRegion
Indicates that a location or area is designated or used as a region for recreational activities.
-
E.
hasRecreationalAspect
Indicates that something includes, involves, or is characterized by a recreational or leisure-related component or purpose.
- 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_69f76ddcc108819097f96853b7ed9ef4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78d7625348190affc0770772de462 |
completed | May 3, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.