Triple
T10672045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubble Space Telescope Science Institute Help Desk |
E251511
|
entity |
| Predicate | handlesQuestionType |
P12351
|
FINISHED |
| Object | technical questions |
—
|
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: technical questions | Statement: [Hubble Space Telescope Science Institute Help Desk, handlesQuestionType, technical questions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handlesQuestionType Context triple: [Hubble Space Telescope Science Institute Help Desk, handlesQuestionType, technical questions]
-
A.
hasAnswerType
Indicates that a question or query is associated with a specific type or category of expected answer.
-
B.
questionType
chosen
Indicates the specific category or kind of question that an item, query, or prompt belongs to.
-
C.
questionnaireType
Indicates the specific category or kind of questionnaire associated with an entity or interaction.
-
D.
handlesOperationType
Indicates that an entity is responsible for processing or managing a specific type or category of operation.
-
E.
basedOnChallengeType
Indicates that something is determined, derived, or configured according to a specific type or category of challenge.
- 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_69d6aa5b0d2881909584b20efc5877f0 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6f8648a248190a3bd284c569152e4 |
completed | April 9, 2026, 12:52 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8a93208190a573061387e2aebb |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:09 p.m.