Triple
T21837192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M930 |
E539148
|
entity |
| Predicate | hasDumpMechanism |
P134343
|
FINISHED |
| Object | hydraulic dump bed |
—
|
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: hydraulic dump bed | Statement: [M930, hasDumpMechanism, hydraulic dump bed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDumpMechanism Context triple: [M930, hasDumpMechanism, hydraulic dump bed]
-
A.
hasMechanism
Indicates that one entity operates, functions, or produces an effect through the specified mechanism or process.
-
B.
hasDepositionSystem
Indicates that one entity possesses, uses, or is characterized by a particular system or method for depositing or laying down material or substances.
-
C.
hasMechanicalFeature
chosen
Indicates that one entity possesses, includes, or is characterized by a specific mechanical component, attribute, or functionality.
-
D.
hasDamFunction
Indicates that something serves the role or performs the function of a dam, such as impounding or regulating the flow of water.
-
E.
hasTriggerMechanism
Indicates that an entity possesses or is equipped with a specific mechanism used to initiate or activate an action or process.
- 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_69e0c475cda88190987d08f23caebdc1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0a7a890208190a902184e60194e1c |
completed | April 28, 2026, 12:27 p.m. |
| PD | Predicate disambiguation | batch_69e6be8c14748190bdcc44a14d50bea4 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:55 p.m.