Triple
T17238694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maple Glade Rain Forest Trail |
E418430
|
entity |
| Predicate | hasAmenitiesNearby |
P5648
|
FINISHED |
| Object | parking area |
—
|
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: parking area | Statement: [Maple Glade Rain Forest Trail, hasAmenitiesNearby, parking area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAmenitiesNearby Context triple: [Maple Glade Rain Forest Trail, hasAmenitiesNearby, parking area]
-
A.
hasNearbyFacility
chosen
Indicates that one entity is located close to or in the vicinity of a particular facility.
-
B.
hasAttractionNearby
Indicates that one entity is located close to another entity that serves as an attraction or point of interest.
-
C.
hasCivicAmenity
Indicates that an entity possesses, provides, or is associated with a public facility or service intended for community use.
-
D.
nearbyUse
Indicates that one entity uses or operates another entity that is located nearby or in close physical proximity.
-
E.
hasRecreationalUseNearby
Indicates that there is at least one location or facility for recreational activities situated close to the referenced 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_69d886d8e96081909870bff6c3d0bf09 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42dfdc8688190aceb223c19a48781 |
completed | April 19, 2026, 1:21 a.m. |
| PD | Predicate disambiguation | batch_69e3832553ac819091aa917c84f755b6 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.