Triple
T15539920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nimrod MRA4 |
E370447
|
entity |
| Predicate | plannedFleetSize |
P51752
|
FINISHED |
| Object | 9 production aircraft |
—
|
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: 9 production aircraft | Statement: [Nimrod MRA4, plannedFleetSize, 9 production aircraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedFleetSize Context triple: [Nimrod MRA4, plannedFleetSize, 9 production aircraft]
-
A.
plannedConstellationSize
Indicates the intended total number of units or elements that are planned to be included in a constellation.
-
B.
fleetSize
Indicates the total number of vehicles, vessels, or units that collectively make up a fleet associated with an entity.
-
C.
numberOfPlannedShips
Indicates the total count of ships that are intended or scheduled to be built, deployed, or used according to a plan.
-
D.
numberPlanned
chosen
Indicates that a specific quantity has been scheduled or intended for a future action or allocation.
-
E.
numberOfAntennasPlanned
Indicates the planned or intended count of antennas associated with an entity or installation.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04430b5188190a555a3cd4fb0c61c |
completed | April 16, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:07 a.m.