Triple
T10216060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Extreme Ultraviolet Explorer |
E242443
|
entity |
| Predicate | studiedObject |
P70296
|
FINISHED |
| Object | hot stars |
—
|
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: hot stars | Statement: [Extreme Ultraviolet Explorer, studiedObject, hot stars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: studiedObject Context triple: [Extreme Ultraviolet Explorer, studiedObject, hot stars]
-
A.
notableObjectOfStudy
Indicates that a subject is a significant or prominent focus of research, analysis, or scholarly attention for another entity.
-
B.
isSubjectOfStudy
chosen
Indicates that an entity is the focus or topic being examined, researched, or analyzed in a study or investigation.
-
C.
studiedProperty
Indicates that an entity has examined, researched, or analyzed a particular property or attribute of another entity.
-
D.
studiedBy
Indicates that a subject (such as a field, topic, or object) is examined, researched, or learned by an agent (such as a person or group).
-
E.
studiedWithin
Indicates that one entity pursued studies or academic work within the scope, context, or boundaries defined by another entity (such as an institution, program, or field).
- 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_69d381ae26c48190985abd0e25ee5d04 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d3aa2894d0819095704449ecc2db6c |
completed | April 6, 2026, 12:42 p.m. |
| PD | Predicate disambiguation | batch_69d3955f61f88190b8d37ff645cd44d3 |
completed | April 6, 2026, 11:13 a.m. |
Created at: April 6, 2026, 11:05 a.m.