Triple
T23157643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marx generator |
E578486
|
entity |
| Predicate | hasOutputCharacteristic |
P274
|
FINISHED |
| Object | fast rise time |
—
|
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: fast rise time | Statement: [Marx generator, hasOutputCharacteristic, fast rise time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutputCharacteristic Context triple: [Marx generator, hasOutputCharacteristic, fast rise time]
-
A.
hasCharacteristic
chosen
Indicates that an entity possesses, exhibits, or is defined by a particular attribute, feature, or quality.
-
B.
hasOutputStatus
Indicates that an entity is associated with a particular state or condition of its produced output.
-
C.
powerOutputCharacteristic
Indicates the relationship between an entity and the specific way its power output behaves or is characterized under given conditions.
-
D.
hasOutputImpedance
Indicates that an entity (such as a device or component) exhibits a specific impedance at its output terminals.
-
E.
hasSerialOutputPin
Indicates that an entity is equipped with a pin or connector dedicated to transmitting data via a serial output interface.
- 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_69e245fb8de081908f0eba7b5fd75bc4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18efe1b0081908e81b757d64c067c |
completed | April 29, 2026, 4:54 a.m. |
| PD | Predicate disambiguation | batch_69ef89ff76808190808ee4ad9dea776b |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:01 p.m.