Triple
T38454688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rudyard Lake |
E912276
|
entity |
| Predicate | hasRecreationalClub |
P30507
|
FINISHED |
| Object | sailing club |
—
|
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: sailing club | Statement: [Rudyard Lake, hasRecreationalClub, sailing club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecreationalClub Context triple: [Rudyard Lake, hasRecreationalClub, sailing club]
-
A.
hasRecreationalOrganization
chosen
Indicates that an entity is associated with, or hosts, a recreational organization such as a club, team, or leisure group.
-
B.
hasRecreationFacility
Indicates that one entity provides, contains, or is equipped with a recreational facility for use by another entity or by the public.
-
C.
hasRecreationalArea
Indicates that an entity includes, provides, or is associated with a designated space intended for leisure or recreational activities.
-
D.
hasRecreationHub
Indicates that an entity serves as or is associated with a central place or facility for recreational activities for another entity.
-
E.
hasRecreationProvider
Indicates that an entity offers or supplies recreational services, facilities, or activities to another entity.
- 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_69f76e84e2dc81908badf05b3aafa9ea |
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:31 p.m.