Triple
T26316115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tonopah and Tidewater Railroad |
E661977
|
entity |
| Predicate | servedResource |
P181025
|
FINISHED |
| Object | silver ore |
—
|
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: silver ore | Statement: [Tonopah and Tidewater Railroad, servedResource, silver ore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedResource Context triple: [Tonopah and Tidewater Railroad, servedResource, silver ore]
-
A.
servedFrom
Indicates that something is provided, delivered, or made available from a particular source or location.
-
B.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
-
C.
isServedFor
Indicates that something is provided or presented as suitable or intended for a particular purpose, use, or recipient.
-
D.
servedWith
Indicates that one item is customarily presented, provided, or consumed together with another as an accompaniment or side.
-
E.
coveredResource
Indicates that one entity serves as a resource that is included within the scope or protection of another entity (such as a policy, agreement, or coverage).
- F. None of above. chosen
Provenance (4 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_69ee812e73048190aae587f1d51e5a06 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
| PDg | Predicate description generation | batch_69f760a2a90c8190b8fbc55412ab752b |
completed | May 3, 2026, 2:50 p.m. |
Created at: April 26, 2026, 10:25 p.m.