Triple
T8588184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KNDS |
E203359
|
entity |
| Predicate | hasKeyCompetence |
P13084
|
FINISHED |
| Object | armored vehicle design |
—
|
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: armored vehicle design | Statement: [KNDS, hasKeyCompetence, armored vehicle design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyCompetence Context triple: [KNDS, hasKeyCompetence, armored vehicle design]
-
A.
hasCompetence
chosen
Indicates that an entity possesses the ability, skill, or qualification to perform a specific task or function effectively.
-
B.
definesCompetenceOf
Indicates that one entity specifies, determines, or establishes the scope, level, or nature of another entity’s competence or capability.
-
C.
hasKeyWork
Indicates that an entity possesses or is associated with a primary or central work (such as a main publication, artwork, or project) that is especially representative or important.
-
D.
hasKeyCapability
Indicates that an entity possesses an essential ability or function that is critical for performing a particular task or role.
-
E.
hasQualification
Indicates that an entity possesses a specific qualification, credential, or competency.
- 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_69ca8329bb7c8190a63c643730839103 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46c5e8888190b721e791c449b0df |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454504448190aaad2af8b17357cd |
completed | March 31, 2026, 10:05 p.m. |
Created at: March 30, 2026, 6:23 p.m.