Triple
T820920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eno River |
E17743
|
entity |
| Predicate | hasTrailNetwork |
P20893
|
FINISHED |
| Object | Eno River State Park trail system |
—
|
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: Eno River State Park trail system | Statement: [Eno River, hasTrailNetwork, Eno River State Park trail system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrailNetwork Context triple: [Eno River, hasTrailNetwork, Eno River State Park trail system]
-
A.
hasTrail
Indicates that an entity possesses, includes, or is associated with a trail or pathway.
-
B.
hasTrailType
Indicates that an entity (such as a trail or route) is associated with a specific type or category of trail.
-
C.
hasTrailLength
Indicates that an entity (such as a trail or route) has a specific measured length.
-
D.
hasNearbyTrail
Indicates that one entity is located close to or within a short distance of a trail.
-
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_69a4937bcaac8190a322524ac6f45a5a |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ab976094819086d676404d745750 |
completed | March 1, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69a4aa76a7808190ac7fd9ba1a4cebcb |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab9634948190b25ea1b2e34df87d |
completed | March 1, 2026, 9:11 p.m. |
Created at: March 1, 2026, 7:38 p.m.