Triple
T24237782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hickling |
E603136
|
entity |
| Predicate | hasRecreationalActivityNearby |
P155301
|
FINISHED |
| Object | boating |
—
|
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: boating | Statement: [Hickling, hasRecreationalActivityNearby, boating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecreationalActivityNearby Context triple: [Hickling, hasRecreationalActivityNearby, boating]
-
A.
hasRecreationalUseNearby
Indicates that there is at least one location or facility for recreational activities situated close to the referenced entity.
-
B.
hasRecreationalOrganization
Indicates that an entity is associated with, or hosts, a recreational organization such as a club, team, or leisure group.
-
C.
hasRecreationalArea
Indicates that an entity includes, provides, or is associated with a designated space intended for leisure or recreational activities.
-
D.
hasAttractionNearby
Indicates that one entity is located close to another entity that serves as an attraction or point of interest.
-
E.
recreationLocation
Indicates the place where a recreational activity or leisure pursuit occurs.
- 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_69e2953f631c819097cbb421046bd417 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28a9c5c3081909cfddc8d29121817 |
completed | April 29, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f1c6d4e99081909f61899eccafb73e |
completed | April 29, 2026, 8:52 a.m. |
Created at: April 18, 2026, 12:03 a.m.