Triple
T2707217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oppenheimer–Volkoff limit |
E59370
|
entity |
| Predicate | typicalValue |
P13474
|
FINISHED |
| Object | about 2 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: about 2 solar masses | Statement: [Oppenheimer–Volkoff limit, typicalValue, about 2 solar masses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalValue Context triple: [Oppenheimer–Volkoff limit, typicalValue, about 2 solar masses]
-
A.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
B.
typicalRange
chosen
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
-
C.
typicalValueForSteel
Indicates that a given value represents a standard or commonly expected value associated with steel under typical conditions.
-
D.
typicalKey
Indicates that the referenced key is the standard or most commonly used key associated with an entity or context.
-
E.
typicalValueForAluminum
Indicates the standard or commonly accepted value (such as a property or parameter) that is characteristic for aluminum 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_69ab4ac66bc88190b9e4afa5fc843f72 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda725f24819090e8d936b3d2d5bc |
completed | March 7, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69abd8224c688190bb4a362360b03007 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.