Triple
T14991347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DUNE |
E373840
|
entity |
| Predicate | dataTakingPlanned |
P26282
|
FINISHED |
| Object | mid-2020s |
—
|
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: mid-2020s | Statement: [DUNE, dataTakingPlanned, mid-2020s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataTakingPlanned Context triple: [DUNE, dataTakingPlanned, mid-2020s]
-
A.
plannedAt
chosen
Indicates that an event, action, or activity is scheduled or intended to occur at a specific time or date.
-
B.
plannedWith
Indicates that an entity created or arranged a plan in collaboration or coordination with another entity.
-
C.
plannedUnder
Indicates that one entity has been scheduled, organized, or arranged to occur within the scope, authority, or framework of another entity.
-
D.
plannedTarget
Indicates that one entity has been designated or selected as the intended target or objective of another entity’s planned action or operation.
-
E.
plannedFrom
Indicates that something is scheduled or arranged to originate, start, or be derived from a specified source, time, or condition.
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded715db408190b44e8a8452c79764 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a6169b48190a679609febd2d0e3 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:53 a.m.