Triple
T4761624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clerget 9B |
E105709
|
entity |
| Predicate | valveOperation |
P49897
|
FINISHED |
| Object | pushrod-operated valves |
—
|
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: pushrod-operated valves | Statement: [Clerget 9B, valveOperation, pushrod-operated valves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: valveOperation Context triple: [Clerget 9B, valveOperation, pushrod-operated valves]
-
A.
valveType
Indicates the specific kind or category of valve associated with an entity or connection.
-
B.
valveCount
Indicates the number of valves associated with an entity, such as a device, system, or component.
-
C.
valveGear
chosen
Indicates that one entity is the valve gear mechanism used to control the operation of another entity, typically an engine or similar machine.
-
D.
valvesPerCylinder
Indicates the number of valves associated with each individual cylinder in an engine.
-
E.
riverControl
Indicates a relationship where one entity manages, regulates, or exerts authority over the flow, usage, or conditions of a river.
- 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650eefe08190b99f9f01b121dbfd |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd6225c9488190afee5bb3619d0365 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:20 p.m.