Triple
T21294666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 4569 |
E524888
|
entity |
| Predicate | hasDeficientNeutralHydrogen |
P143624
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [NGC 4569, hasDeficientNeutralHydrogen, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDeficientNeutralHydrogen Context triple: [NGC 4569, hasDeficientNeutralHydrogen, true]
-
A.
containsNeutralHydrogen
Indicates that one entity has within it or is composed of neutral (non-ionized) hydrogen associated with the other entity.
-
B.
hasNeutralHydrogenMass
Indicates that an entity possesses a specified amount of mass in the form of neutral (non-ionized) hydrogen.
-
C.
hasNeutralHydrogenTails
Indicates that an object possesses extended structures or tails composed of neutral hydrogen gas.
-
D.
hasNeutralHydrogenEnvelope
Indicates that an object is surrounded by an extended region or layer composed primarily of neutral (non-ionized) hydrogen gas.
-
E.
usesHydrogenAtomDonor
Indicates that one entity employs another entity as a source of hydrogen atoms (a hydrogen donor) in a chemical or biochemical process.
- F. None of above. chosen
Provenance (4 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_69e0b517e6748190850d6f6ddf323d69 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73857784881908c3b8418a4c00c1e |
completed | April 21, 2026, 8:41 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
| PDg | Predicate description generation | batch_69e6190163448190a2404b396215c686 |
completed | April 20, 2026, 12:16 p.m. |
Created at: April 16, 2026, 4:04 p.m.