Triple
T11952562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mastic Trail |
E284460
|
entity |
| Predicate | isHikingTrail |
P102446
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Mastic Trail, isHikingTrail, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHikingTrail Context triple: [Mastic Trail, isHikingTrail, true]
-
A.
isRailTrail
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.
isPartOfTrailSystem
Indicates that something belongs to, or is included within, a larger trail network or trail system.
-
C.
TrailLinkIs
Indicates that one trail segment is connected to or continues from another trail segment.
-
D.
hasHikingTrailToTop
Indicates that there exists a hiking trail leading from a starting location to the top or summit of a specified destination.
-
E.
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.
- F. None of above. chosen
Provenance (4 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d90365da288190a132703df563de23 |
completed | April 10, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3e48e08190b2fee43af4f57323 |
completed | April 10, 2026, 8:56 a.m. |
| PDg | Predicate description generation | batch_69d8dd0ba0f88190b7d5e358c27ca184 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 8, 2026, 9:45 p.m.