Triple
T10641807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington and Old Dominion Railroad |
E250739
|
entity |
| Predicate | trackUsageAfterClosure |
P59269
|
FINISHED |
| Object | rail trail |
—
|
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: rail trail | Statement: [Washington and Old Dominion Railroad, trackUsageAfterClosure, rail trail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackUsageAfterClosure Context triple: [Washington and Old Dominion Railroad, trackUsageAfterClosure, rail trail]
-
A.
trackUsage
Indicates that one entity monitors and records how another entity or resource is being used over time.
-
B.
closureFrequency
Indicates how often a particular process, event, or entity is closed or brought to an end within a given period.
-
C.
trackAccess
Indicates that one entity monitors, records, or keeps a log of another entity’s access or usage of a resource.
-
D.
conditionAfterClosure
chosen
Indicates the state or circumstances that exist after a process, event, or entity has been formally closed or concluded.
-
E.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
- 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_69d6aa5a4c4881908f39be6efe5981e5 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6dfce1ddc8190893fe6f7b047b56b |
completed | April 8, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69d6dd83b114819098e84dc658e82d7e |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:05 p.m.