Triple
T33748865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andrews family (local railroad officials) |
E864778
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | railroad officials family |
C49567
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: railroad officials family Context triple: [Andrews family (local railroad officials), instanceOf, railroad officials family]
-
A.
railroad official family
chosen
A railroad official family is a household whose primary breadwinner holds an administrative or managerial position within a railway organization, shaping the family’s social status, lifestyle, and connection to the rail industry.
-
B.
multiple-unit train family
A multiple-unit train family is a group of closely related self-propelled rail vehicles sharing a common design platform, modular components, and performance characteristics, configured in fixed or semi-permanent sets for passenger or freight service.
-
C.
passenger railcar family
A passenger railcar family is a group of related rail vehicles sharing a common design platform, structural features, and systems, adapted into multiple variants to serve different passenger transport roles and service requirements.
-
D.
fern family
A fern family is a taxonomic group of closely related fern genera that share common evolutionary traits, reproductive structures, and morphological characteristics.
-
E.
group of railway officers
A group of railway officers is a collective of officials responsible for planning, managing, and overseeing the safe and efficient operation of railway services and infrastructure.
- F. None of above.
Provenance (1 batch)
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_69f3498c35f881909df279ae4270f831 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:45 a.m.