Triple
T3804528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eurofighter Typhoon Tranche 3 |
E91771
|
entity |
| Predicate | hasWeaponCompatibility |
P17728
|
FINISHED |
| Object | air-to-air missiles |
—
|
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: air-to-air missiles | Statement: [Eurofighter Typhoon Tranche 3, hasWeaponCompatibility, air-to-air missiles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWeaponCompatibility Context triple: [Eurofighter Typhoon Tranche 3, hasWeaponCompatibility, air-to-air missiles]
-
A.
hasWeaponType
Indicates that an entity is associated with or equipped with a specific type or category of weapon.
-
B.
supportsWeapon
chosen
Indicates that one entity is capable of accommodating, using, or being compatible with a specified weapon.
-
C.
armedBy
Indicates that one entity is supplied with weapons, equipment, or armaments by another entity.
-
D.
associatedWithWeapon
Indicates that an entity has a connection or involvement with a weapon, such as ownership, use, presence, or relevance in a given context.
-
E.
weaponTypeTested
Indicates that a specific type of weapon has been subjected to a test or evaluation in the described context.
- 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_69aed96354f48190a768966d6bd19b04 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aee8db8a288190afd1e3b9dcf02e97 |
completed | March 9, 2026, 3:35 p.m. |
| PD | Predicate disambiguation | batch_69aee7461abc8190945716f4b93e1a18 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:15 p.m.