Triple
T37259817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Altitude Water Cherenkov Observatory |
E924228
|
entity |
| Predicate | operationalDutyCycle |
P89574
|
FINISHED |
| Object | >90% |
—
|
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: >90% | Statement: [High Altitude Water Cherenkov Observatory, operationalDutyCycle, >90%]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationalDutyCycle Context triple: [High Altitude Water Cherenkov Observatory, operationalDutyCycle, >90%]
-
A.
operationalPeak
Indicates the highest level or period of performance, capacity, or activity that a system, process, or entity reaches during its operation.
-
B.
dutyTime
Indicates the period during which an entity is officially on duty or expected to perform assigned responsibilities.
-
C.
operatingCycle
Indicates the duration or process through which an entity completes a full sequence of its operations from start to finish.
-
D.
operationalCharacteristic
chosen
Indicates a relationship where a specific functional or performance trait is attributed to, or used to describe, how an entity operates.
-
E.
numberOperational
Indicates that an entity is currently functioning and available for use in its intended operational capacity.
- 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_69f76eabd6c481909d414a80a1345c98 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a022348ae2881908eae1be79b6f6ff6 |
completed | May 11, 2026, 6:43 p.m. |
| PD | Predicate disambiguation | batch_6a0220beb6b08190981fb86363757517 |
completed | May 11, 2026, 6:32 p.m. |
Created at: May 3, 2026, 4:15 p.m.