Triple
T25475106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grail |
E638409
|
entity |
| Predicate | systemFamily |
P17743
|
FINISHED |
| Object | Strela MANPADS family |
—
|
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: Strela MANPADS family | Statement: [Grail, systemFamily, Strela MANPADS family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: systemFamily Context triple: [Grail, systemFamily, Strela MANPADS family]
-
A.
platformFamily
chosen
Indicates that one platform belongs to, or is categorized under, a broader family or group of related platforms.
-
B.
systemName
Indicates that an entity has a specific system-level name or identifier assigned to it.
-
C.
frameworkFamily
Indicates that one framework belongs to the same overarching family or lineage as another framework, typically sharing core principles, architecture, or origin.
-
D.
operatingSystemFamilyMember
Indicates that one operating system belongs to, or is a variant within, a broader operating system family.
-
E.
systemSymbol
Indicates that one entity serves as the symbolic representation or notation used within a particular system for another entity or concept.
- 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_69e75db9b964819096802dcf502e577e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f60c3b09488190ade1b69ff7f0df0e |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 21, 2026, 2:25 p.m.