Triple
T7454859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boilermakers |
E172095
|
entity |
| Predicate | nicknameOriginField |
P64332
|
FINISHED |
| Object | engineering and railroad boiler work |
—
|
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: engineering and railroad boiler work | Statement: [Boilermakers, nicknameOriginField, engineering and railroad boiler work]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nicknameOriginField Context triple: [Boilermakers, nicknameOriginField, engineering and railroad boiler work]
-
A.
nickNameGivenBy
Indicates that one entity assigns or uses a particular nickname for another entity.
-
B.
nicknamePattern
Indicates that one entity serves as a nickname or informal name pattern for another entity.
-
C.
namesakeDescription
Indicates that the object provides a descriptive explanation of why or how the subject is considered a namesake of something or someone.
-
D.
namesakeFullName
Indicates that one entity’s full name is used as the namesake or source of the name for another entity.
-
E.
nameEtymologyFor
chosen
Indicates that one entity expresses or explains the origin or derivation of the name of another entity.
- 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_69c68a66554c8190add75c65942c0317 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f3addd648190b618bfbffe08db2c |
completed | March 27, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69c6f039f7248190bb4183f97b605763 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:14 p.m.