Triple
T27528881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Energy Stereoscopic System |
E694912
|
entity |
| Predicate | HESSIConfiguration |
P44358
|
FINISHED |
| Object | four 12-m telescopes in square layout |
—
|
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: four 12-m telescopes in square layout | Statement: [High Energy Stereoscopic System, HESSIConfiguration, four 12-m telescopes in square layout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HESSIConfiguration Context triple: [High Energy Stereoscopic System, HESSIConfiguration, four 12-m telescopes in square layout]
-
A.
telescopeConfiguration
chosen
Indicates the specific setup or arrangement of components and settings used to operate a telescope.
-
B.
detectorConfiguration
Indicates a relationship where a detector is associated with, or operates under, a specific configuration or set of parameter settings.
-
C.
constellationConfiguration
Indicates the specific spatial arrangement and relative positioning of elements within a constellation.
-
D.
missionConfiguration
Indicates the specific setup, parameters, and conditions under which a mission is planned or executed.
-
E.
hornConfiguration
Indicates how the horns of an entity are arranged, shaped, or configured in relation to each other.
- 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_69ef538608b081908b9f659bb09d5e0f |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62f31e12c8190880b758fef6a07e0 |
completed | May 2, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69f623ac3a9c8190a6ee0c137b09e4b0 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 1:25 p.m.