Triple
T9671771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dreadnought-class nuclear-powered ballistic missile submarines |
E234046
|
entity |
| Predicate | numberOfPlannedUnits |
P21287
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [Dreadnought-class nuclear-powered ballistic missile submarines, numberOfPlannedUnits, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfPlannedUnits Context triple: [Dreadnought-class nuclear-powered ballistic missile submarines, numberOfPlannedUnits, 4]
-
A.
numberPlanned
Indicates that a specific quantity has been scheduled or intended for a future action or allocation.
-
B.
numberOfRulesPlanned
Indicates the planned or intended count of rules associated with an entity or process.
-
C.
numberOfUnits
Indicates the quantity or count of discrete units associated with an entity or relationship.
-
D.
plannedUnder
Indicates that one entity has been scheduled, organized, or arranged to occur within the scope, authority, or framework of another entity.
-
E.
numberOfPlannedShips
chosen
Indicates the total count of ships that are intended or scheduled to be built, deployed, or used according to a plan.
- 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_69ca848f55e48190b3f67252571c3d45 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c6949108190b699442e5c2aacf9 |
completed | April 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b5d40c8190850ad7a351445f32 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:15 p.m.