Triple
T24824596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FLASH free-electron laser |
E621153
|
entity |
| Predicate | pulseProperty |
P55008
|
FINISHED |
| Object | ultra-intense pulses |
—
|
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: ultra-intense pulses | Statement: [FLASH free-electron laser, pulseProperty, ultra-intense pulses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pulseProperty Context triple: [FLASH free-electron laser, pulseProperty, ultra-intense pulses]
-
A.
pulseDuration
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.
signalProperty
chosen
Indicates that one entity has a specific characteristic, attribute, or feature related to a signal.
-
D.
hasPulsations
Indicates that an entity exhibits rhythmic, repeated pulsating behavior or variations over time.
-
E.
beatCharacteristic
Indicates a characteristic or quality that defines or describes a particular beat (such as its style, pattern, or rhythmic property).
- 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_69e2fac0c3b881909110e5a56c6fa46f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:05 a.m.