Triple
T25842319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Attack-class submarine |
E650968
|
entity |
| Predicate | replacedByProgram |
P29646
|
FINISHED |
| Object | AUKUS nuclear-powered submarine program |
—
|
NE NERFINISHED |
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: AUKUS nuclear-powered submarine program | Statement: [Attack-class submarine, replacedByProgram, AUKUS nuclear-powered submarine program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedByProgram Context triple: [Attack-class submarine, replacedByProgram, AUKUS nuclear-powered submarine program]
-
A.
reprogrammedBy
Indicates that an entity’s original programming or code has been altered or replaced by another specified agent or process.
-
B.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by another entity.
-
C.
formerProgram
Indicates that an entity previously held the role or status of a program but no longer does so.
-
D.
replacedWith
chosen
Indicates that one entity has been substituted or superseded by another entity, taking over its role, function, or position.
-
E.
replacedByRule
Indicates that an entity has been superseded or substituted by another entity according to a specific rule or transformation.
- 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_69e7ab38086081908f3a8e7e0c6efd83 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 22, 2026, 7:50 a.m.