Triple
T18541291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UGC 7408 |
E453104
|
entity |
| Predicate | hasDominantComponent |
P59278
|
FINISHED |
| Object | neutral hydrogen |
—
|
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: neutral hydrogen | Statement: [UGC 7408, hasDominantComponent, neutral hydrogen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDominantComponent Context triple: [UGC 7408, hasDominantComponent, neutral hydrogen]
-
A.
hasDominantUse
Indicates that one use or function of an entity is primary or prevailing over its other possible uses.
-
B.
hasDominantTree
Indicates that one tree in a given context or area is the primary or most influential tree relative to others.
-
C.
hasMajorComponent
Indicates that one entity includes another entity as a primary or most significant component or part.
-
D.
dominantComposition
chosen
Indicates that one entity is the primary or prevailing component, material, or element that makes up or characterizes another entity.
-
E.
dominantComplex
Indicates that one entity exerts primary control, influence, or prominence over another within a given context 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_69d8d387b5548190aa030dad2cb4947e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e534b749b88190ad03b26bee3c89df |
completed | April 19, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69e469e274a48190a570b25cfef4d890 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:37 a.m.