Triple
T28247438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashley River Road National Scenic Byway |
E712205
|
entity |
| Predicate | hasSiteAlongRoute |
P86982
|
FINISHED |
| Object | Drayton Hall |
—
|
NE NERFINISHED |
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: Drayton Hall | Statement: [Ashley River Road National Scenic Byway, hasSiteAlongRoute, Drayton Hall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSiteAlongRoute Context triple: [Ashley River Road National Scenic Byway, hasSiteAlongRoute, Drayton Hall]
-
A.
hasAlongRoute
Indicates that one entity lies on or is situated along the path, course, or route taken by another entity.
-
B.
isPartOfRoute
Indicates that something (such as a segment, stop, or step) belongs to and is contained within a larger route.
-
C.
situatedOnTransportRoute
chosen
Indicates that one entity is located along, on, or directly adjacent to a specified transport route (such as a road, railway, or shipping lane).
-
D.
locatedOnRouteTo
Indicates that one entity lies along the path or course taken when traveling from a starting point to a specified destination.
-
E.
routeAlong
Indicates that one entity follows, runs parallel to, or is situated along the course or path defined by another entity.
- 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_69efb51fb98881909692421959ec0170 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 27, 2026, 11:02 p.m.