Triple
T36572805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Astrosat |
E902162
|
entity |
| Predicate | SXTFullForm |
P2351
|
FINISHED |
| Object | Soft X-ray Telescope |
—
|
NE NERFINISHED |
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: Soft X-ray Telescope | Statement: [Astrosat, SXTFullForm, Soft X-ray Telescope]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SXTFullForm Context triple: [Astrosat, SXTFullForm, Soft X-ray Telescope]
-
A.
extantForm
Indicates that a given entity currently exists in a particular form or manifestation.
-
B.
expandedForm
Indicates that one representation is the expanded or fully written-out form of another, typically decomposing it into a sum or more detailed expression.
-
C.
hasFullForm
chosen
Indicates that one entity is the complete, expanded, or unabbreviated form of another entity.
-
D.
standardizedFormOf
Indicates that one entity is the normalized or officially standardized version of another, often consolidating variations or alternative forms into a single canonical form.
-
E.
standardFormUsedIn
Indicates that a particular standard form is employed or applied within a given context, process, or system.
- 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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.