Triple
T28390198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allendale Campus |
E719131
|
entity |
| Predicate | hasOutdoorRecreationAreas |
P5383
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Allendale Campus, hasOutdoorRecreationAreas, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutdoorRecreationAreas Context triple: [Allendale Campus, hasOutdoorRecreationAreas, yes]
-
A.
hasRecreationalArea
chosen
Indicates that an entity includes, provides, or is associated with a designated space intended for leisure or recreational activities.
-
B.
hasOutdoorResource
Indicates that an entity is associated with, provides, or includes access to an outdoor resource or facility.
-
C.
isOutdoorRecreationSite
Indicates that a place is designated or used primarily for recreational activities that take place outdoors.
-
D.
hasCoastalRecreation
Indicates that an entity provides, supports, or is associated with recreational activities occurring along a coast or shoreline.
-
E.
isRecreationalArea
Indicates that a place or space is designated and used primarily for leisure, relaxation, or recreational activities.
- 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 28, 2026, 1:13 a.m.