Triple
T4163708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | inflationary universe theory |
E84390
|
entity |
| Predicate | expansionRate |
P39818
|
FINISHED |
| Object | exponential |
—
|
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: exponential | Statement: [inflationary universe theory, expansionRate, exponential]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionRate Context triple: [inflationary universe theory, expansionRate, exponential]
-
A.
expansionNumber
Indicates the specific expansion sequence or identifier assigned to an entity within a series of related additions or extensions.
-
B.
expansionType
chosen
Indicates the specific manner or category by which something grows, extends, or increases in scope or size.
-
C.
expansionStatus
Indicates the current state or phase of growth, enlargement, or extension of something relative to its previous or intended size or scope.
-
D.
expands
Indicates that one entity increases in size, volume, scope, or extent relative to a previous state or another entity.
-
E.
expansionReason
Indicates the reason or cause behind an expansion event or process occurring between entities.
- 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_69aed932cab48190b80ffe35f7029ae1 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0321eee88190871c1d4bf44a5007 |
completed | March 9, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69af018dc90c8190a754b1bfbc802e80 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:44 p.m.