Triple
T26316099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tonopah and Tidewater Railroad |
E661977
|
entity |
| Predicate | servedCompany |
P64086
|
FINISHED |
| Object | Pacific Coast Borax Company |
—
|
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: Pacific Coast Borax Company | Statement: [Tonopah and Tidewater Railroad, servedCompany, Pacific Coast Borax Company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedCompany Context triple: [Tonopah and Tidewater Railroad, servedCompany, Pacific Coast Borax Company]
-
A.
servesCompany
chosen
Indicates that one entity provides services or performs duties in support of a company.
-
B.
selectedCompany
Indicates that a particular company has been chosen or designated from a set of possible companies.
-
C.
underlyingCompanyService
Indicates that one entity functions as a foundational or supporting service for another company or business entity.
-
D.
memberCompany
Indicates that a company is formally part of, or affiliated as a member with, a larger organization, group, or association.
-
E.
ownedCompany
Indicates that one entity possesses legal ownership or controlling interest in another entity that is a company.
- 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_69ee812e73048190aae587f1d51e5a06 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: April 26, 2026, 10:25 p.m.