Triple
T6669711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T-346A |
E151693
|
entity |
| Predicate | hasHardpoints |
P28002
|
FINISHED |
| Object | underwing pylons |
—
|
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: underwing pylons | Statement: [T-346A, hasHardpoints, underwing pylons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHardpoints Context triple: [T-346A, hasHardpoints, underwing pylons]
-
A.
hardpoints
chosen
Indicates a relationship where one entity provides designated attachment locations or mounting interfaces on its structure for connecting other components or equipment.
-
B.
hasTurrets
Indicates that an entity is equipped with or possesses one or more turrets.
-
C.
weaponCapability
Indicates that one entity has the ability to use, deploy, or function as a weapon against another entity or target.
-
D.
hasArmedWing
Indicates that an entity maintains, controls, or is associated with an organized armed or military wing.
-
E.
internalWeaponsBays
Indicates that an entity is equipped with weapons storage or launch systems housed within its internal structure rather than mounted externally.
- 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_69c687f71fc081909dbd45d6377f6045 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ce738fe88190a5557900efeec7ec |
completed | March 27, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69c6ad09974c81908784300ae218961f |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:02 p.m.