Triple
T8538553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nebula |
E202137
|
entity |
| Predicate | modifiedWith |
P43320
|
FINISHED |
| Object | cybernetic enhancements |
—
|
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: cybernetic enhancements | Statement: [Nebula, modifiedWith, cybernetic enhancements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modifiedWith Context triple: [Nebula, modifiedWith, cybernetic enhancements]
-
A.
modification
chosen
Indicates a change made to an existing entity, altering its properties, structure, or state from a prior version.
-
B.
laterModification
Indicates that one entity is a modification or revision that occurs after another in time.
-
C.
mayBeModifiedBy
Indicates that an entity has the potential to be altered, changed, or updated by another entity or process.
-
D.
amendedBy
Indicates that one entity has been modified, revised, or updated as a result of changes made by another entity.
-
E.
amendedFor
Indicates that one entity has been modified or revised specifically to address, correct, or accommodate 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_69ca832355b08190b8b6a4ab4a4a3554 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe6a7441c8190980c3516073422fe |
completed | March 31, 2026, 3:22 p.m. |
| PD | Predicate disambiguation | batch_69cbd111bf988190be98c92a607c6456 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:18 p.m.