Triple
T1083549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Bang nucleosynthesis |
E24000
|
entity |
| Predicate | startsWhen |
P12708
|
FINISHED |
| Object | universe cools below about 1 billion kelvin |
—
|
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: universe cools below about 1 billion kelvin | Statement: [Big Bang nucleosynthesis, startsWhen, universe cools below about 1 billion kelvin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startsWhen Context triple: [Big Bang nucleosynthesis, startsWhen, universe cools below about 1 billion kelvin]
-
A.
startsAt
Indicates that an event, process, or state begins at a specific time, location, or point in a sequence.
-
B.
occursWhen
chosen
Indicates that one event or condition happens at the same time or is triggered under the circumstances defined by another event or condition.
-
C.
startDate
Indicates the point in time when an event, state, or relationship begins.
-
D.
beganWith
Indicates that one event, process, or state started with or was initiated by another specified event, process, or state.
-
E.
endsOn
Indicates that one entity terminates or concludes precisely at the boundary or endpoint of another entity.
- 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_69a49404428c819092dcc9632f5f7b8b |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b95e56948190a1e92367ad7240b7 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b73f4310819086281f8ec67d1a32 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.