Triple
T2370715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | function generator |
E46082
|
entity |
| Predicate | hasOutputMode |
P12713
|
FINISHED |
| Object | continuous wave output |
—
|
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: continuous wave output | Statement: [function generator, hasOutputMode, continuous wave output]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutputMode Context triple: [function generator, hasOutputMode, continuous wave output]
-
A.
hasOutputType
Indicates that an entity produces, returns, or yields a result of a specified type.
-
B.
hasOutputStructure
Indicates that an entity produces, defines, or is associated with a particular structural form or arrangement as its output.
-
C.
hasWorkingMode
chosen
Indicates that an entity operates under or supports a particular mode or configuration of functioning.
-
D.
hasAccessMode
Indicates the type or method of access that one entity is permitted to use with respect to another entity or resource.
-
E.
hasFinalFormat
Indicates that an entity possesses or is associated with its completed, finalized version or representation.
- 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_69a88a145268819083e2736cb835c696 |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abc76f5aec8190867d621e6849258c |
completed | March 7, 2026, 6:36 a.m. |
| PD | Predicate disambiguation | batch_69abc59b88348190a2d6c08f69974117 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:56 p.m.