Triple
T22382002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | X-ray free-electron lasers |
E553296
|
entity |
| Predicate | typicalPulseDuration |
P81277
|
FINISHED |
| Object | femtosecond timescale |
—
|
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 timescale | Statement: [X-ray free-electron lasers, typicalPulseDuration, femtosecond timescale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPulseDuration Context triple: [X-ray free-electron lasers, typicalPulseDuration, femtosecond timescale]
-
A.
pulseDuration
chosen
Indicates the length of time that a pulse or discrete signal remains active or at a specified level.
-
B.
pulsePeriodStability
Indicates how consistently the time interval between successive pulses remains the same over repeated measurements.
-
C.
pulsationPeriod_hours
Indicates the duration, measured in hours, of one complete pulsation cycle of an object or system.
-
D.
hasTypicalPerformanceDuration
Indicates the usual or expected length of time that a performance or activity typically lasts.
-
E.
typicalNumberOfCycles
Indicates the usual or characteristic count of cycles associated with an entity, process, or event.
- 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_69e11e4c03248190a26a5060ea6973ee |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1582cce608190b5324b30f349a3ff |
completed | April 29, 2026, 1 a.m. |
| PD | Predicate disambiguation | batch_69e73015484c8190a9a0b9f554b61a81 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:45 p.m.