Triple
T7319319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scarboro Pond |
E168496
|
entity |
| Predicate | hasRecreationalPathType |
P17835
|
FINISHED |
| Object | loop trail |
—
|
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: loop trail | Statement: [Scarboro Pond, hasRecreationalPathType, loop trail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecreationalPathType Context triple: [Scarboro Pond, hasRecreationalPathType, loop trail]
-
A.
hasRecreationalRoute
chosen
Indicates that an entity is associated with or includes a route intended for recreational activities such as walking, cycling, or hiking.
-
B.
isRecreationalArea
Indicates that a place or space is designated and used primarily for leisure, relaxation, or recreational activities.
-
C.
hasRecreationType
Indicates that an entity is associated with or offers a particular type or category of recreational activity.
-
D.
hasRecreationalArea
Indicates that an entity includes, provides, or is associated with a designated space intended for leisure or recreational activities.
-
E.
hasRecreationClassification
Indicates that an entity is assigned a specific type or category of recreational use or activity.
- 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_69c68a5251508190ad68df4151cfeb04 |
completed | March 27, 2026, 1:46 p.m. |
| NER | Named-entity recognition | batch_69c6ef18b7bc81908a9ee405d684f304 |
completed | March 27, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69c6e7705f4881909793071dee50c557 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:02 p.m.