Triple
T24547290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HIP 61173 |
E607259
|
entity |
| Predicate | dominantElement |
P59278
|
FINISHED |
| Object | 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: hydrogen | Statement: [HIP 61173, dominantElement, hydrogen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantElement Context triple: [HIP 61173, dominantElement, hydrogen]
-
A.
dominantClass
Indicates that one class or category holds primary authority, influence, or precedence over others within a given context.
-
B.
dominantComplex
Indicates that one entity exerts primary control, influence, or prominence over another within a given context or system.
-
C.
dominantCluster
Indicates that one cluster in a set is the most influential or representative group relative to the others, often based on size, centrality, or impact.
-
D.
dominantComposition
chosen
Indicates that one entity is the primary or prevailing component, material, or element that makes up or characterizes another entity.
-
E.
dominantOn
Indicates that one entity exerts control, authority, or prevailing influence over another in a given context.
- 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_69e2c4c9bf94819082d05da6f5c29907 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8caba8c819082c3bf33b6ff9cd0 |
completed | April 30, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:27 a.m.