Triple
T26541767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thud |
E671406
|
entity |
| Predicate | notableVariantRole |
P88519
|
FINISHED |
| Object | Wild Weasel SEAD (F-105G) |
—
|
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: Wild Weasel SEAD (F-105G) | Statement: [Thud, notableVariantRole, Wild Weasel SEAD (F-105G)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableVariantRole Context triple: [Thud, notableVariantRole, Wild Weasel SEAD (F-105G)]
-
A.
notableMemberVariant
Indicates that an entity is a specific variant or version of a notable member within a group, class, or category.
-
B.
laterVariantRole
Indicates that one role is a subsequent or later variant of another, reflecting a modified or evolved version of the original role.
-
C.
notableArcRole
Indicates that one entity holds a particularly important or prominent role within a narrative arc or storyline in relation to another entity.
-
D.
notableVariation
chosen
Indicates that one entity represents a significant or noteworthy deviation or difference from another entity within a given context.
-
E.
notableHolderRole
Indicates that an entity is recognized for holding a particular role, office, or position in a notable or distinguished capacity.
- 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_69eeb3206e748190b90c85cc81f38c91 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69fedfd913f48190bdcd450980868d9a |
completed | May 9, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fedf58c6e88190821a7156054c9086 |
completed | May 9, 2026, 7:16 a.m. |
Created at: April 27, 2026, 1:42 a.m.