Triple
T30856513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Town of The Blue Mountains |
E785934
|
entity |
| Predicate | hasMajorRecreation |
P971
|
FINISHED |
| Object | skiing |
—
|
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: skiing | Statement: [Town of The Blue Mountains, hasMajorRecreation, skiing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorRecreation Context triple: [Town of The Blue Mountains, hasMajorRecreation, skiing]
-
A.
hasRecreationalAspect
Indicates that something includes, involves, or is characterized by a recreational or leisure-related component or purpose.
-
B.
hasRecreationPurpose
Indicates that something is used or intended to be used for recreational or leisure activities.
-
C.
hasRecreationActivity
chosen
Indicates that an entity provides, includes, or is associated with a particular recreational activity.
-
D.
hasRecreationalArea
Indicates that an entity includes, provides, or is associated with a designated space intended for leisure or recreational activities.
-
E.
hasRecreationFacility
Indicates that one entity provides, contains, or is equipped with a recreational facility for use by another entity or by the public.
- 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_69f224b91c14819084e764832fe67a57 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ffdf47d9608190830ca23d9cef6409 |
completed | May 10, 2026, 1:28 a.m. |
| PD | Predicate disambiguation | batch_69ffdf00e2b4819082dd5cb78f316baf |
completed | May 10, 2026, 1:27 a.m. |
Created at: April 29, 2026, 8:46 p.m.