Triple
T6030904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunken Road |
E134298
|
entity |
| Predicate | tourRoute |
P17534
|
FINISHED |
| Object | stop on the Antietam driving tour |
—
|
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: stop on the Antietam driving tour | Statement: [Sunken Road, tourRoute, stop on the Antietam driving tour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tourRoute Context triple: [Sunken Road, tourRoute, stop on the Antietam driving tour]
-
A.
tourPattern
Indicates a recurring or structured sequence of visits or stops that defines how a tour is organized or carried out.
-
B.
hasTouristRoute
chosen
Indicates that a location or site is connected to or included in a designated tourist route or itinerary.
-
C.
tourWith
Indicates that one entity accompanies another on a tour, sharing the same itinerary or guided experience.
-
D.
tourDocumented
Indicates that a tour has been recorded or documented, typically capturing its details, events, or progression.
-
E.
pilgrimageRouteTo
Indicates a route or path that is traditionally used or designated for making a religious or spiritual pilgrimage to a particular destination.
- 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_69c0087515148190a97475d412563865 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056af89e881909652957f94317684 |
completed | March 22, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69c049e9a68c81909da0cfe4779ce9b5 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:08 p.m.