Triple
T17684168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B53 nuclear bomb |
E440845
|
entity |
| Predicate | approximateNumberProduced |
P99700
|
FINISHED |
| Object | about 340 units |
—
|
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: about 340 units | Statement: [B53 nuclear bomb, approximateNumberProduced, about 340 units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateNumberProduced Context triple: [B53 nuclear bomb, approximateNumberProduced, about 340 units]
-
A.
approximateProductionNumber
chosen
Indicates that one entity specifies an estimated or non-exact quantity associated with the production output of another entity.
-
B.
approximateNumberAwarded
Indicates the estimated quantity of awards or recognitions given in a particular context or event.
-
C.
mineCountApproximate
Indicates that the number of mines associated with an entity is estimated or roughly counted rather than known exactly.
-
D.
approximates
Indicates that one entity is close to, but not exactly equal to, the value, form, or behavior of another entity.
-
E.
designedApproximately
Indicates that one entity was created, planned, or engineered to an estimated or imprecise degree in relation to another entity or specification.
- 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4704710488190826aaf0bdd4b2088 |
completed | April 19, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69e3cde3673c8190a889e14ba1f07dc1 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 10:02 a.m.