Triple
T9729319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Putnam County Trailway |
E235697
|
entity |
| Predicate | railTrailConversion |
P57725
|
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: [Putnam County Trailway, railTrailConversion, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railTrailConversion Context triple: [Putnam County Trailway, railTrailConversion, yes]
-
A.
isRailTrail
chosen
Indicates that a path or route is a rail trail, meaning it follows or repurposes a former or existing railway corridor for recreational or transportation use.
-
B.
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.
-
C.
trailName
Indicates the name assigned to a specific trail or path in the relationship.
-
D.
railTracks
Indicates that one entity consists of, includes, or is associated with rail tracks used for guiding trains or rail vehicles.
-
E.
trailDesignation
Indicates that a particular label, name, or classification has been assigned to a trail to identify its route, type, or official status.
- 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_69ca84d0fad481909cdd45aa77416c48 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9eafa3a88190bc62924d94b89cd8 |
completed | April 1, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69cd03c6ffc88190a5e9569e19122ad5 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:21 p.m.