Triple
T18513201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bourget |
E452393
|
entity |
| Predicate | recreationalActivitiesNearby |
P85424
|
FINISHED |
| Object | hiking in Larose Forest |
—
|
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: hiking in Larose Forest | Statement: [Bourget, recreationalActivitiesNearby, hiking in Larose Forest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recreationalActivitiesNearby Context triple: [Bourget, recreationalActivitiesNearby, hiking in Larose Forest]
-
A.
hasRecreationalUseNearby
Indicates that there is at least one location or facility for recreational activities situated close to the referenced entity.
-
B.
recreationLocation
Indicates the place where a recreational activity or leisure pursuit occurs.
-
C.
nearbyResortArea
Indicates that a resort area is located close to or within a short distance of a specified place or entity.
-
D.
nearbyActivity
chosen
Indicates that an activity occurs close in space or proximity to a specified entity or location.
-
E.
nearbyEvent
Indicates that one event occurs close in space or time to another event.
- 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53348274c8190a82861b0104538e3 |
completed | April 19, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69e469dbf5208190b6fc49e02a087f54 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:36 a.m.