Triple
T34582334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kroupa initial mass function |
E887941
|
entity |
| Predicate | hasUpperMassLimit |
P93654
|
FINISHED |
| Object | approximately 100 solar masses |
—
|
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: approximately 100 solar masses | Statement: [Kroupa initial mass function, hasUpperMassLimit, approximately 100 solar masses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUpperMassLimit Context triple: [Kroupa initial mass function, hasUpperMassLimit, approximately 100 solar masses]
-
A.
hasUpperDeadweightLimit
Indicates that there is a specified maximum deadweight capacity or load limit applicable to an entity.
-
B.
hasRestMassUpperBound
chosen
Indicates that there is a specified maximum possible value for the rest mass of an entity.
-
C.
hasHighMass
Indicates that an entity possesses a mass that is large or above a specified threshold relative to a given standard or context.
-
D.
hasMassScale
Indicates that an entity is associated with a particular mass measurement scale or system used to quantify its mass.
-
E.
weightLimitLowerBoundKg
Indicates the minimum allowable weight, in kilograms, that satisfies a specified limit or constraint.
- 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_69f349d25cbc8190869998de5915886b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f720c4ac8c8190a90b3e3d82d8c10d |
completed | May 3, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:03 a.m.