Triple
T156325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milky Way |
E3188
|
entity |
| Predicate | formationEpoch |
P2559
|
FINISHED |
| Object | shortly after the Big Bang |
—
|
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: shortly after the Big Bang | Statement: [Milky Way, formationEpoch, shortly after the Big Bang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formationEpoch Context triple: [Milky Way, formationEpoch, shortly after the Big Bang]
-
A.
firstDeployed
Indicates the time or event when something (such as a system, product, or resource) was initially put into active use or operation.
-
B.
emergedAround
chosen
Indicates that something came into existence or became noticeable at approximately a particular time or period.
-
C.
editionNumber
Indicates the specific sequential number assigned to an edition of a work within its series of published versions.
-
D.
beganOfficialNumberingWith
Indicates that an entity started its formal or official numbering sequence with a specified initial number or identifier.
-
E.
firstDeployedFor
Indicates that an entity was initially deployed or put into operational use specifically for another entity (such as a project, mission, or organization).
- 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a258808ff08190a06b6206f635612b |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a2565ded588190a27319aaa0130b4f |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.