Triple
T5815153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andromeda XVIII |
E128965
|
entity |
| Predicate | hasGas |
P22265
|
FINISHED |
| Object | no significant neutral hydrogen detected |
—
|
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: no significant neutral hydrogen detected | Statement: [Andromeda XVIII, hasGas, no significant neutral hydrogen detected]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGas Context triple: [Andromeda XVIII, hasGas, no significant neutral hydrogen detected]
-
A.
hasFuel
Indicates that an entity possesses or contains fuel available for use.
-
B.
hasFuelStorage
Indicates that one entity possesses or is equipped with a facility, container, or system used to store fuel for later use.
-
C.
isGasPoor
Indicates that an entity has a relatively low amount or abundance of gas compared to a relevant standard or reference.
-
D.
gasSystem
Indicates a relationship where an entity functions as, is part of, or is associated with a gas-based system used for distribution, control, or processing of gases.
-
E.
gasContent
chosen
Indicates that one entity has, contains, or is characterized by a certain amount or type of gas.
- 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_69c0084788848190bcf71f6bc5d71597 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0400f1af881908d376ea4793f6dea |
completed | March 22, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69c0333fdd7081908d829265caa2ac11 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:53 p.m.