Triple
T31145123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry Braithwaite Abbott |
E793901
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Canadian railway official |
C8521
|
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: Canadian railway official Context triple: [Henry Braithwaite Abbott, instanceOf, Canadian railway official]
-
A.
Canadian public official
A Canadian public official is an individual who holds a position of authority or responsibility within federal, provincial, territorial, or municipal government institutions in Canada, serving the public interest and implementing laws, policies, and programs.
-
B.
Canadian engineer
A Canadian engineer is a professional trained in engineering disciplines who applies scientific and technical knowledge to design, develop, and maintain systems, structures, or technologies within the context of Canadian standards, regulations, and societal needs.
-
C.
railway worker
chosen
A railway worker is an individual responsible for the operation, maintenance, safety, and support services of trains and railway infrastructure.
-
D.
Canadian contractor
A Canadian contractor is an individual or business entity based in Canada that provides specialized services or labor to clients under a contractual agreement, typically on a temporary or project-by-project basis.
-
E.
railway infrastructure manager
A railway infrastructure manager is an entity responsible for the planning, construction, maintenance, operation, and safe management of railway tracks, signaling systems, and related fixed installations.
- 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:06 p.m.