Triple
T3729275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IXPE |
E79021
|
entity |
| Predicate | scienceCapability |
P6774
|
FINISHED |
| Object | imaging X-ray polarimetry |
—
|
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: imaging X-ray polarimetry | Statement: [IXPE, scienceCapability, imaging X-ray polarimetry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scienceCapability Context triple: [IXPE, scienceCapability, imaging X-ray polarimetry]
-
A.
plannedCapability
Indicates that an entity is intended or scheduled to possess or provide a particular capability in the future.
-
B.
isCapableOf
Indicates that an entity has the ability or capacity to perform a particular action or function.
-
C.
scienceReturn
Indicates that an action or process yields scientific data, findings, or value as its outcome.
-
D.
orbitCapability
Indicates that one entity has the ability or suitability to orbit around another entity.
-
E.
technologicalFeature
chosen
Indicates that one entity possesses, exhibits, or is characterized by a specific technological capability, component, or functionality in relation to another entity.
- 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_69ad8b0e4650819090ad7cef094285e8 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb17432881909390284b935ed3fd |
completed | March 8, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69adc0452f5081909c79e114a86cce8c |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.