Triple
T24812034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V-600 |
E620815
|
entity |
| Predicate | systemCategory |
P64612
|
FINISHED |
| Object | short- to medium-range air defense system |
—
|
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: short- to medium-range air defense system | Statement: [V-600, systemCategory, short- to medium-range air defense system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: systemCategory Context triple: [V-600, systemCategory, short- to medium-range air defense system]
-
A.
componentCategory
Indicates that one entity is classified as belonging to a particular component category of another entity.
-
B.
functionCategory
Indicates that one function is classified as belonging to a particular functional category or type.
-
C.
system
Indicates that an entity functions as or belongs to a structured, organized set of components or processes that operate together as a system.
-
D.
coreCategory
chosen
Indicates that one entity is the primary or fundamental category to which another entity belongs or is classified under.
-
E.
systemEntry
Indicates that an entity is being recorded, registered, or introduced into a particular system or structured environment.
- 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_69e2fabfd4648190bd0e5c7f4dbb6cab |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 4:50 a.m.