Triple
T17115598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Ambush |
E415328
|
entity |
| Predicate | reactorRefuellingInterval |
P123193
|
FINISHED |
| Object | life-of-ship core |
—
|
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: life-of-ship core | Statement: [HMS Ambush, reactorRefuellingInterval, life-of-ship core]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reactorRefuellingInterval Context triple: [HMS Ambush, reactorRefuellingInterval, life-of-ship core]
-
A.
typicalFuelCycleLength
chosen
Indicates the usual duration of a complete fuel usage and replacement cycle for a system or process.
-
B.
PM-3AReactorOperationalUntil
Indicates that a specific PM-3A reactor remained in an operational state up to a given point in time.
-
C.
nrcReactorUnitNumber
Indicates the specific unit number assigned to a nuclear reactor within an NRC-licensed facility.
-
D.
plannedNumberOfReactors
Indicates the total number of reactors that are intended or scheduled to be built, installed, or operated for a given facility or project.
-
E.
reactor3CommissioningDate
Indicates the date on which the third reactor in a series was formally commissioned and entered into operational service.
- 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3e80528588190a877dcc6d6d3a392 |
completed | April 18, 2026, 8:22 p.m. |
| PD | Predicate disambiguation | batch_69e35d6b1b988190a8d6b6fe78c35e59 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.