Triple

T2443000
Position Surface form Disambiguated ID Type / Status
Subject Shockley–Queisser limit E53321 entity
Predicate appliesUnder P1129 FINISHED
Object standard AM1.5G solar spectrum for terrestrial applications 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: standard AM1.5G solar spectrum for terrestrial applications | Statement: [Shockley–Queisser limit, appliesUnder, standard AM1.5G solar spectrum for terrestrial applications]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: appliesUnder
Context triple: [Shockley–Queisser limit, appliesUnder, standard AM1.5G solar spectrum for terrestrial applications]
  • A. appliesAt
    Indicates that an action, rule, or condition is relevant to or in effect at a specific location, context, or point in time.
  • B. appliesFrom
    Indicates that a rule, condition, or effect begins to be applicable starting from a specific point in time or state.
  • C. appliesTo chosen
    Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
  • D. appliesOver
    Indicates that one entity’s effect, rule, or condition extends across or is valid for a specified range, domain, or set of entities.
  • E. appliesAcross
    Indicates that a condition, rule, or property holds uniformly over multiple items, cases, or contexts.
  • 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_69ab495b6dac8190ac82661aa1452222 completed March 6, 2026, 9:38 p.m.
NER Named-entity recognition batch_69abcabf477081908512df63ac1a6414 completed March 7, 2026, 6:50 a.m.
PD Predicate disambiguation batch_69abc5ad8e588190b97c4cd7cf575043 completed March 7, 2026, 6:29 a.m.
Created at: March 6, 2026, 9:43 p.m.