Triple
T30981038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arcata and Mad River Railroad |
E789372
|
entity |
| Predicate | primaryIndustryServed |
P2193
|
FINISHED |
| Object | timber industry |
—
|
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: timber industry | Statement: [Arcata and Mad River Railroad, primaryIndustryServed, timber industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryIndustryServed Context triple: [Arcata and Mad River Railroad, primaryIndustryServed, timber industry]
-
A.
primaryServes
Indicates that one entity’s main or principal function is to serve, support, or provide service to another entity.
-
B.
supportedIndustry
Indicates that one entity provides backing, resources, or services to help sustain or advance a particular industry.
-
C.
sectorServed
chosen
Indicates the industry or economic sector that an entity primarily serves or targets with its activities, products, or services.
-
D.
professionServed
Indicates that an entity has performed work or provided services in a particular profession or occupational role.
-
E.
organizationTypeServed
Indicates the type of organization that is served or supported by a given entity or activity.
- 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_69f224c4831c8190be53924ec25a150a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a0357f9670081908a7ba1cd46a0b46a |
completed | May 12, 2026, 4:40 p.m. |
| PD | Predicate disambiguation | batch_6a03575e3258819093303248d1569f95 |
completed | May 12, 2026, 4:37 p.m. |
Created at: April 29, 2026, 8:55 p.m.