Triple
T38633634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W-53 |
E937521
|
entity |
| Predicate | strategicClassification |
P180385
|
FINISHED |
| Object | offensive strategic weapon |
—
|
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: offensive strategic weapon | Statement: [W-53, strategicClassification, offensive strategic weapon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strategicClassification Context triple: [W-53, strategicClassification, offensive strategic weapon]
-
A.
classificationOf
chosen
Indicates that one entity serves as a classification, category, or type under which another entity is grouped or organized.
-
B.
areClassifiedBy
Indicates that entities are assigned to one or more categories, types, or classes according to a specified classification scheme.
-
C.
classified
Indicates that one entity has assigned another entity to a specific category, group, or type based on defined criteria.
-
D.
classificationIntroduced
Indicates that one entity has introduced or established a particular classification or categorization for another entity.
-
E.
classificationSymbol
Indicates that one entity serves as a symbol, label, or marker used to classify or categorize another entity.
- 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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.