Triple
T32530017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petersburg and Weldon Railroad |
E831425
|
entity |
| Predicate | supplyRouteTo |
P161596
|
FINISHED |
| Object | Petersburg, Virginia |
—
|
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: Petersburg, Virginia | Statement: [Petersburg and Weldon Railroad, supplyRouteTo, Petersburg, Virginia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supplyRouteTo Context triple: [Petersburg and Weldon Railroad, supplyRouteTo, Petersburg, Virginia]
-
A.
supplyBy
Indicates that one entity is provided, furnished, or made available by another entity as its source or supplier.
-
B.
supplyLine
chosen
Indicates a logistical connection through which resources, goods, or support are transported from a source to a destination.
-
C.
supplyMode
Indicates the manner or method by which something is provided, delivered, or made available.
-
D.
supplyRole
Indicates that an entity provides or fulfills a specific role within a supply or provisioning relationship to another entity.
-
E.
supplyPort
Indicates that one entity serves as a source or interface through which resources, materials, or energy are provided to 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_69f34924b1cc8190ad3aca0c0f012a7e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c51ba4248190b98f43a5866bab0d |
completed | May 3, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:01 a.m.