Triple
T16897166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minor Hubbell Keith |
E424335
|
entity |
| Predicate | associatedIndustryViaFamily |
P110506
|
FINISHED |
| Object | railroads |
—
|
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: railroads | Statement: [Minor Hubbell Keith, associatedIndustryViaFamily, railroads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedIndustryViaFamily Context triple: [Minor Hubbell Keith, associatedIndustryViaFamily, railroads]
-
A.
relationToIndustry
Indicates how an entity is connected or relevant to a particular industry, such as through involvement, impact, or association.
-
B.
hasRelativeInSameIndustry
chosen
Indicates that one entity has a relative who works in the same industry as the entity.
-
C.
hasParentCompanyIndustry
Indicates that an entity’s parent company operates in, or is associated with, a specified industry.
-
D.
associatedIndustrySite
Indicates that one entity is linked or related to another entity that represents an industry-specific website or online resource.
-
E.
containsIndustry
Indicates that one entity includes or encompasses a particular industry within its scope, structure, or operations.
- 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_69d889da3e8c8190a2b118f383f0beac |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3c8d880208190ad2b2c8616b54ea3 |
completed | April 18, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69e32b9489408190bcb2ede567ff5bf9 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:29 a.m.