Triple
T12080538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | erbium-doped fiber amplifier |
E287664
|
entity |
| Predicate | typicalOutputPower |
P89369
|
FINISHED |
| Object | +10 to +23 dBm |
—
|
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: +10 to +23 dBm | Statement: [erbium-doped fiber amplifier, typicalOutputPower, +10 to +23 dBm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalOutputPower Context triple: [erbium-doped fiber amplifier, typicalOutputPower, +10 to +23 dBm]
-
A.
powerOutputW
Indicates the amount of power produced or delivered by an entity, measured in watts.
-
B.
powerOutputType
Indicates the specific form or category of power output associated with an entity, such as electrical, mechanical, or thermal.
-
C.
powerOutputApprox
Indicates an approximate or estimated value for the power output produced by an entity or system.
-
D.
designPowerOutput
Indicates the intended or specified power output level that something is designed to produce under defined conditions.
-
E.
typicalPower
chosen
Indicates the usual or characteristic amount of power associated with an entity under normal operating conditions.
- 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_69d6ab4964708190850585628b287b0c |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902bf4f508190842927e7e0642235 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:48 p.m.