Triple
T2704446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Bang |
E59308
|
entity |
| Predicate | hasOpenQuestions |
P42093
|
FINISHED |
| Object | nature of dark energy |
—
|
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: nature of dark energy | Statement: [Big Bang, hasOpenQuestions, nature of dark energy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpenQuestions Context triple: [Big Bang, hasOpenQuestions, nature of dark energy]
-
A.
hasKeyQuestion
Indicates that one entity possesses or is associated with a primary or central question relevant to another entity.
-
B.
canAnswerQuestions
Indicates that an entity has the ability or capacity to respond correctly or appropriately to questions.
-
C.
openingQuestion
Indicates that one entity poses an initial or introductory question to another, typically at the start of an interaction or dialogue.
-
D.
numberOfQuestions
Indicates the total count of questions associated with or contained in a given entity or context.
-
E.
opened
Indicates that one entity caused another entity (such as an object, container, or passage) to change from a closed or inaccessible state to an open or accessible state.
- F. None of above. chosen
Provenance (4 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_69abda518c58819096c8b67c0f754655 |
completed | March 7, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69abd82062988190b4292f242ad70b2c |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd9ceec708190aa162399023b2273 |
completed | March 7, 2026, 7:54 a.m. |
Created at: March 6, 2026, 9:55 p.m.