Triple
T8588268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KNDS |
E203361
|
entity |
| Predicate | hasCoreCompetency |
P52737
|
FINISHED |
| Object | design of armored vehicles |
—
|
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: design of armored vehicles | Statement: [KNDS, hasCoreCompetency, design of armored vehicles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoreCompetency Context triple: [KNDS, hasCoreCompetency, design of armored vehicles]
-
A.
hasCompetence
Indicates that an entity possesses the ability, skill, or qualification to perform a specific task or function effectively.
-
B.
hasProfessionalCore
chosen
Indicates that an entity possesses a central set of professional skills, knowledge, or competencies that define its primary professional function or expertise.
-
C.
hasCoreFacility
Indicates that an entity possesses, hosts, or is equipped with a central, shared facility that supports key operations or services.
-
D.
hasCoreValue
Indicates that an entity possesses or is characterized by a fundamental guiding principle or core belief.
-
E.
hasCore
Indicates that one entity possesses, contains, or is built around a central or most essential component represented by 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_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.