Triple
T20074554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omega laser system |
E499825
|
entity |
| Predicate | primaryPulseDuration |
P81277
|
FINISHED |
| Object | nanosecond-scale |
—
|
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: nanosecond-scale | Statement: [Omega laser system, primaryPulseDuration, nanosecond-scale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryPulseDuration Context triple: [Omega laser system, primaryPulseDuration, nanosecond-scale]
-
A.
pulseDuration
chosen
Indicates the length of time that a pulse or discrete signal remains active or at a specified level.
-
B.
primaryRhythmSource
Indicates that one entity serves as the main provider or origin of the rhythmic pattern for another entity.
-
C.
pulsationPeriod_hours
Indicates the duration, measured in hours, of one complete pulsation cycle of an object or system.
-
D.
firstPulseAssociatedWith
Indicates that a given entity is linked to the initial or earliest pulse in a sequence of pulses.
-
E.
pulsePeriodStability
Indicates how consistently the time interval between successive pulses remains the same over repeated measurements.
- 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_69da627770948190997f486f9a2e370f |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66439efe881909a068c3f05022421 |
completed | April 20, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69e54cf369b88190931532420517dac7 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:40 p.m.