Triple
T328513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crescent Meadow |
E6572
|
entity |
| Predicate | hasTrailUse |
P2401
|
FINISHED |
| Object | pedestrian only |
—
|
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: pedestrian only | Statement: [Crescent Meadow, hasTrailUse, pedestrian only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrailUse Context triple: [Crescent Meadow, hasTrailUse, pedestrian only]
-
A.
hasTrail
Indicates that an entity possesses, includes, or is associated with a trail or pathway.
-
B.
hasHumanUse
Indicates that something is used, employed, or utilized by humans for a particular purpose or benefit.
-
C.
hasTrailType
chosen
Indicates that an entity (such as a trail or route) is associated with a specific type or category of trail.
-
D.
hasRailTrail
Indicates that one location or entity possesses, includes, or is connected by a rail trail (a recreational trail converted from or running along a former or existing railway corridor) to another location or entity.
-
E.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
- 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_69a2e7933d6c8190bb2592ad13286ef2 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eaad37b0819085beda2a491da9a8 |
completed | Feb. 28, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69a2e94aab1c8190b8654708c87eeb91 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.