Triple
T25277796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K-2SO |
E633746
|
entity |
| Predicate | droidClass |
P111330
|
FINISHED |
| Object | security |
—
|
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: security | Statement: [K-2SO, droidClass, security]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: droidClass Context triple: [K-2SO, droidClass, security]
-
A.
designClass
Indicates that one entity is the design or blueprint class from which the other entity is derived or instantiated.
-
B.
platformClass
Indicates the classification or category assigned to a platform, specifying what type or class of platform it is.
-
C.
clase
chosen
Indicates a classification or type relationship, where one entity is categorized as belonging to a particular class or category defined by another entity.
-
D.
Nova 3Class
Indicates a classification relationship where an entity is categorized as belonging to the "Nova 3" class.
-
E.
densityClass
Indicates the classification of an entity based on its density level or range.
- 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_69e75a9402fc81909362ca85277c06d9 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48ba8e99081908b3fd911e8634dcc |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:18 p.m.