Triple
T3716875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A-4 Skyhawk |
E81551
|
entity |
| Predicate | maxOrdnanceLoad |
P49953
|
FINISHED |
| Object | about 9,900 lb |
—
|
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 9,900 lb | Statement: [A-4 Skyhawk, maxOrdnanceLoad, about 9,900 lb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxOrdnanceLoad Context triple: [A-4 Skyhawk, maxOrdnanceLoad, about 9,900 lb]
-
A.
armamentCapacity
chosen
Indicates the maximum quantity or type of weapons or munitions that something is designed or allowed to carry.
-
B.
ammunitionCapacity
Indicates the maximum amount of ammunition that something (typically a weapon or container) is designed to hold at one time.
-
C.
maximumTonnageLimitedBy
Indicates that the maximum allowable tonnage of one entity is constrained or capped by the capacity or limit specified by another entity.
-
D.
weaponCapability
Indicates that one entity has the ability to use, deploy, or function as a weapon against another entity or target.
-
E.
designedCargoCapacity
Indicates the maximum amount of cargo an object (such as a vehicle or container) was originally engineered or specified to carry.
- 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_69ad8b1a81588190b3f27a5483bb610e |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adc9d087c881909f6d2ec6e518fb02 |
completed | March 8, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69adc0436e508190909ec4a3e8443aef |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:33 p.m.