Triple
T20047245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leo IV Dwarf Galaxy |
E497592
|
entity |
| Predicate | hasDynamicalMassToLightRatio |
P135105
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Leo IV Dwarf Galaxy, hasDynamicalMassToLightRatio, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDynamicalMassToLightRatio Context triple: [Leo IV Dwarf Galaxy, hasDynamicalMassToLightRatio, high]
-
A.
massToLightRatio
Indicates the relationship between an object's total mass and its luminosity, expressing how much mass corresponds to each unit of emitted light.
-
B.
dynamicalMass_solarMasses
Indicates the dynamical mass of an object or system expressed in units of the Sun’s mass.
-
C.
hasGasToStellarMassRatio
Indicates the proportion between an object's gas mass and its stellar mass.
-
D.
hasVirialMass
chosen
Indicates that an entity possesses a mass value determined via the virial theorem, typically inferred from its internal motions or dynamics.
-
E.
hasStellarMassClass
Indicates the classification relationship that assigns an object to a specific category based on its stellar mass.
- 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_69da627278c88190babe4297a9df1236 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6632b2de48190abe2b277d89eb695 |
completed | April 20, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:37 p.m.