Triple
T8171422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Front Royal, Virginia |
E190828
|
entity |
| Predicate | hasRiverRecreation |
P1477
|
FINISHED |
| Object | canoeing on the Shenandoah River |
—
|
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: canoeing on the Shenandoah River | Statement: [Front Royal, Virginia, hasRiverRecreation, canoeing on the Shenandoah River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiverRecreation Context triple: [Front Royal, Virginia, hasRiverRecreation, canoeing on the Shenandoah River]
-
A.
hasRiverActivity
chosen
Indicates that an entity engages in, supports, or is associated with activities occurring on or along a river.
-
B.
recreationAccess
Indicates that one entity provides or has the ability to use recreational facilities, activities, or spaces associated with another entity.
-
C.
hasRaftingDifficulty
Indicates that an entity is associated with a specific level of rafting difficulty.
-
D.
hasBoatRamp
Indicates that a location provides a designated ramp or launch area for putting boats into the water or taking them out.
-
E.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
- 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_69ca82c1c0a08190bf8692b4d91a03ca |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb48056d0c819094575090a41e0083 |
completed | March 31, 2026, 4:05 a.m. |
| PD | Predicate disambiguation | batch_69cb36a4c40c81909f60aef0e1624c13 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:39 p.m.