Triple
T24949665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marion Steam Shovel Company |
E624291
|
entity |
| Predicate | hasMachineryClass |
P167033
|
FINISHED |
| Object | rail-mounted steam shovels |
—
|
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: rail-mounted steam shovels | Statement: [Marion Steam Shovel Company, hasMachineryClass, rail-mounted steam shovels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMachineryClass Context triple: [Marion Steam Shovel Company, hasMachineryClass, rail-mounted steam shovels]
-
A.
hasMechanicalFeature
Indicates that one entity possesses, includes, or is characterized by a specific mechanical component, attribute, or functionality.
-
B.
hasPreservedMachinery
Indicates that an entity retains machinery that has been kept in its original or functional condition rather than removed or replaced.
-
C.
hasMechanism
Indicates that one entity operates, functions, or produces an effect through the specified mechanism or process.
-
D.
hadClassOf
Indicates that an entity previously belonged to or was categorized under a particular class or type.
-
E.
hasCarClass
Indicates that one entity is associated with, or categorized under, a particular class or type of car.
- F. None of above. chosen
Provenance (4 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_69e2ff22e4c48190a0444b5a044f14e8 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f6653ccf648190b65fb1141928e47e |
completed | May 2, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f663ff176c8190aaadb475f75daee4 |
completed | May 2, 2026, 8:52 p.m. |
Created at: April 18, 2026, 5:55 a.m.