Triple
T20047244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leo IV Dwarf Galaxy |
E497592
|
entity |
| Predicate | hasBaryonContent |
P57006
|
FINISHED |
| Object | low |
—
|
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: low | Statement: [Leo IV Dwarf Galaxy, hasBaryonContent, low]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBaryonContent Context triple: [Leo IV Dwarf Galaxy, hasBaryonContent, low]
-
A.
hasBaryonNumber
Indicates that an entity possesses a specific baryon number, quantifying its net content of baryonic matter (baryons minus antibaryons).
-
B.
baryonicContent
chosen
Indicates the proportion or amount of ordinary (baryonic) matter associated with or contained within an astronomical object or system.
-
C.
baryonNumber
Indicates that a specified baryon number (a conserved quantum number related to the count of baryons minus antibaryons) is assigned to or associated with an entity or interaction.
-
D.
hasBarycenter
Indicates that one entity serves as the barycenter (center of mass) of another entity or system.
-
E.
hasTotalQuarkContent
Indicates that an entity (such as a particle or system) is associated with a specified total number or combination of quarks it contains.
- 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.