Triple
T37704106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ti:sapphire laser |
E939151
|
entity |
| Predicate | gainBandwidth |
P189152
|
FINISHED |
| Object | >200 nm |
—
|
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: >200 nm | Statement: [Ti:sapphire laser, gainBandwidth, >200 nm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gainBandwidth Context triple: [Ti:sapphire laser, gainBandwidth, >200 nm]
-
A.
increasesBandwidthToward
Indicates that one entity causes an increase in the available data transmission capacity directed toward another entity.
-
B.
lowerBandWidth
Indicates that one entity has a smaller or more limited bandwidth capacity than another.
-
C.
bandWidthProportionalTo
Indicates that the bandwidth of one entity varies in direct proportion to the bandwidth of another entity.
-
D.
topBandWidth
Indicates the maximum data transfer capacity or throughput available at the upper limit of a connection, channel, or system.
-
E.
bandwidthEfficiency
Indicates how effectively available bandwidth is utilized to transmit data relative to capacity or resource usage.
- F. None of above. chosen
Provenance (4 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_69f76edb49dc8190b951dce9ce6ef789 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbb083ab708190a18b045311106f27 |
completed | May 6, 2026, 9:20 p.m. |
Created at: May 3, 2026, 4:18 p.m.