Triple
T20236110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A-7 Corsair II |
E498151
|
entity |
| Predicate | maxPayload |
P10871
|
FINISHED |
| Object | approximately 15,000 lb of ordnance |
—
|
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: approximately 15,000 lb of ordnance | Statement: [A-7 Corsair II, maxPayload, approximately 15,000 lb of ordnance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxPayload Context triple: [A-7 Corsair II, maxPayload, approximately 15,000 lb of ordnance]
-
A.
maximumPayload
chosen
Indicates the greatest amount of load or capacity that an entity is designed or allowed to carry, handle, or support.
-
B.
externalPayloadCapacity
Indicates the maximum weight of payload that can be carried externally (outside the main body or cargo area) by an entity.
-
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.
weightLimitInPounds
Indicates the maximum allowable weight for something, expressed in pounds.
-
E.
weightLimitInKilograms
Indicates the maximum allowable weight for something, expressed in kilograms.
- 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_69da6274c58c81909c646eabed6f4f30 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6716a5af0819095ea419a4d1f0d1d |
completed | April 20, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69e55b18609481909ab28bc8750a642f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:40 p.m.