Triple
T3628766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grumman TBF Avenger |
E76902
|
entity |
| Predicate | torpedoCapacity |
P13762
|
FINISHED |
| Object | 1 Mark 13 torpedo |
—
|
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: 1 Mark 13 torpedo | Statement: [Grumman TBF Avenger, torpedoCapacity, 1 Mark 13 torpedo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: torpedoCapacity Context triple: [Grumman TBF Avenger, torpedoCapacity, 1 Mark 13 torpedo]
-
A.
armamentTorpedoes
chosen
Indicates that an entity is equipped with torpedoes as part of its armament or weaponry.
-
B.
numberOfTorpedoesHit
Indicates the number of torpedoes that successfully struck a specified target.
-
C.
ammunitionCapacity
Indicates the maximum amount of ammunition that something (typically a weapon or container) is designed to hold at one time.
-
D.
antiSubmarineArmament
Indicates the type or presence of weapons or equipment specifically designed for anti-submarine warfare associated with an entity.
-
E.
paratroopCapacity
Indicates the maximum number of paratroopers or amount of airborne troops that something (typically a vehicle or vessel) is capable of carrying or deploying.
- 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_69ad85dc03948190b35b7189e4175bcc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc2df2b708190afef6925a53ec551 |
completed | March 8, 2026, 6:41 p.m. |
| PD | Predicate disambiguation | batch_69adb8410a5881909c94818d7060b2b0 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.