Triple
T11665243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | chirped pulse amplification |
E277231
|
entity |
| Predicate | typicalPulseDurationRange |
P13474
|
FINISHED |
| Object | femtosecond to picosecond |
—
|
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: femtosecond to picosecond | Statement: [chirped pulse amplification, typicalPulseDurationRange, femtosecond to picosecond]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPulseDurationRange Context triple: [chirped pulse amplification, typicalPulseDurationRange, femtosecond to picosecond]
-
A.
pulseDuration
Indicates the length of time that a pulse or discrete signal remains active or at a specified level.
-
B.
typicalRuntimeRange
Indicates the usual lower and upper bounds of time typically required for an entity to run or complete its operation.
-
C.
typicalRange
chosen
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
-
D.
pulsePeriodStability
Indicates how consistently the time interval between successive pulses remains the same over repeated measurements.
-
E.
typicalSupplyVoltageRange
Indicates the usual minimum-to-maximum voltage range within which a device or component is designed to be normally powered and operate correctly.
- 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_69d6aafd0a448190b44da30af8c6c519 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a43f438081909da476294a057c38 |
completed | April 10, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69d88a73f9ac819095662042804bf40a |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:39 p.m.