Triple
T11260446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Base Delta 1 |
E266546
|
entity |
| Predicate | dateRenamedAsSpaceBaseDelta |
P27702
|
FINISHED |
| Object | 2021 |
—
|
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: 2021 | Statement: [Space Base Delta 1, dateRenamedAsSpaceBaseDelta, 2021]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateRenamedAsSpaceBaseDelta Context triple: [Space Base Delta 1, dateRenamedAsSpaceBaseDelta, 2021]
-
A.
renamedDueTo
Indicates that one entity was renamed as a consequence of another specified cause, event, or condition.
-
B.
formsDeltaIn
Indicates that one entity creates or shapes a delta landform within or at the mouth of another entity (typically a body of water or region).
-
C.
dateChangesWith
chosen
Indicates that the date associated with one entity is altered or updated in conjunction with, or as a result of, a change involving another entity.
-
D.
formsDeltaAt
Indicates that one entity creates or gives rise to a change, difference, or deviation (a “delta”) in another entity at a specific point or context.
-
E.
hasDeltaName
Indicates that an entity has an alternative or changed name (a “delta” name) associated with it.
- 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_69d6aac7953c8190b82caf9d7640fdf9 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e936cb048190b4d6fb2851ef8932 |
completed | April 9, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69d7879bc56c8190b2e8d2193f29de05 |
completed | April 9, 2026, 11:03 a.m. |
Created at: April 8, 2026, 9:31 p.m.