Triple
T36185140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agusta A129 Mangusta |
E1046823
|
entity |
| Predicate | exportVariantBasisFor |
P165518
|
FINISHED |
| Object | TAI T129 ATAK |
—
|
NE NERFINISHED |
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: TAI T129 ATAK | Statement: [Agusta A129 Mangusta, exportVariantBasisFor, TAI T129 ATAK]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exportVariantBasisFor Context triple: [Agusta A129 Mangusta, exportVariantBasisFor, TAI T129 ATAK]
-
A.
exportVariantOf
Indicates that one entity is an exported version or externally released form derived from another, original entity.
-
B.
baseVariant
chosen
Indicates that one entity serves as the original or primary version from which another related variant is derived.
-
C.
rulesVariantOf
Indicates that one set of rules is a modified or alternative version derived from another set of rules.
-
D.
governsVariant
Indicates a regulatory relationship where one entity controls, influences, or determines the behavior or state of a specific variant of another entity.
-
E.
exportVariantName
Indicates that one entity is the name or label of a specific variant of another entity intended for export.
- 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_69f76e3d4fbc81908c159c7beeb4ce00 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.