Triple
T2730656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eddington limit |
E60303
|
entity |
| Predicate | typicalCompositionAssumption |
P8601
|
FINISHED |
| Object | fully ionized 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: fully ionized hydrogen | Statement: [Eddington limit, typicalCompositionAssumption, fully ionized hydrogen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCompositionAssumption Context triple: [Eddington limit, typicalCompositionAssumption, fully ionized hydrogen]
-
A.
typicalAssumption
Indicates that something is taken as a standard or default assumption that generally holds in typical or normal circumstances.
-
B.
standardComposition
chosen
Indicates that one entity is composed or constructed according to a recognized or conventional standard defined by another entity.
-
C.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
D.
typicalPractice
Indicates that an action, behavior, or method is commonly or customarily done in a given context or by a given group.
-
E.
assumes
Indicates that one entity takes on, accepts, or presumes a role, responsibility, state, or fact regarding another entity or situation.
- 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_69ab4b75cd908190b691ef0d1801acda |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdaee29088190bc4c734e48995794 |
completed | March 7, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69abd82586f88190a98f60d3247fe2d3 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.