Triple
T1114454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union Pacific Railway Act of 1862 |
E11064
|
entity |
| Predicate | bondAmountPerMile |
P482
|
FINISHED |
| Object | $16,000 per mile on level grade |
—
|
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: $16,000 per mile on level grade | Statement: [Union Pacific Railway Act of 1862, bondAmountPerMile, $16,000 per mile on level grade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bondAmountPerMile Context triple: [Union Pacific Railway Act of 1862, bondAmountPerMile, $16,000 per mile on level grade]
-
A.
fareBasis
Indicates the specific fare rule or pricing category that applies to a ticket or travel segment.
-
B.
hasToll
Indicates that the use, access, or passage associated with something requires payment of a toll or fee.
-
C.
fareCapping
Indicates a limit on the total amount a rider can be charged for fares over a set period, after which additional trips are free or discounted.
-
D.
monetaryValue
chosen
Indicates the amount of money associated with an entity, event, or transaction.
-
E.
creditPercentage
Indicates the proportion or share of credit assigned to an entity in relation to a particular outcome, contribution, or transaction.
- 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_69a493252a648190ac48f8742474a5e8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bbd92a8c8190a16e55f3f739010f |
completed | March 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69a4bb42990c819080db96478fd4977e |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:43 p.m.