Triple
T17179287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HiRISE |
E416938
|
entity |
| Predicate | detectorConfiguration |
P126630
|
FINISHED |
| Object | pushbroom scanner |
—
|
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: pushbroom scanner | Statement: [HiRISE, detectorConfiguration, pushbroom scanner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: detectorConfiguration Context triple: [HiRISE, detectorConfiguration, pushbroom scanner]
-
A.
detectorType
Indicates the specific kind or category of detector associated with an entity or measurement.
-
B.
vertexDetectorTechnology
Indicates the specific detection technology or method used in the vertex detector component of a particle physics or tracking system.
-
C.
detectorFormat
Indicates the specific data or signal representation used by a detector to encode or output its measurements.
-
D.
numberOfDetectors
Indicates the quantity of detectors associated with or involved in a given entity or system.
-
E.
detectorConcept
Indicates that one entity functions as a detector whose conceptual design, type, or detection principle is characterized or specified by the other entity.
- 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_69d886d5f34c8190b24564dfaa63f3fb |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3fc0f9a288190b0ddfb673bd8e84b |
completed | April 18, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e383141ae0819096acd71683637cbc |
completed | April 18, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69e39c2fedb881908bfed2c3e5f2616a |
completed | April 18, 2026, 2:58 p.m. |
Created at: April 10, 2026, 5:37 a.m.