Triple
T8177738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FERMI free-electron laser |
E190979
|
entity |
| Predicate | pulseType |
P39320
|
FINISHED |
| Object | ultra-short light 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-short light pulses | Statement: [FERMI free-electron laser, pulseType, ultra-short light pulses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pulseType Context triple: [FERMI free-electron laser, pulseType, ultra-short light pulses]
-
A.
peakType
Indicates the specific classification or category of a peak based on its form, prominence, or other defining characteristics.
-
B.
signalType
Indicates the specific kind or category of signal associated with or used by an entity or interaction.
-
C.
waveType
chosen
Indicates the specific kind or category of wave associated with an entity or interaction (e.g., type of signal, motion, or oscillation).
-
D.
vibrationPattern
Indicates a specific recurring sequence or configuration of vibrations exhibited by or applied to an entity.
-
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_69ca82c4538081909404325aa5639483 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4abb66bc81908d758c7af2e23ac6 |
completed | March 31, 2026, 4:16 a.m. |
| PD | Predicate disambiguation | batch_69cb36a7952481908f34e3e82f375a84 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:40 p.m.