Triple
T2062165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koops |
E45814
|
entity |
| Predicate | defenseStyle |
P13663
|
FINISHED |
| Object | uses shell for protection |
—
|
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: uses shell for protection | Statement: [Koops, defenseStyle, uses shell for protection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defenseStyle Context triple: [Koops, defenseStyle, uses shell for protection]
-
A.
defenseResult
Indicates the outcome or consequence of a defensive action or strategy in response to an attack or threat.
-
B.
defends
Indicates that one entity protects or supports another entity against attack, criticism, or harm.
-
C.
defensiveTactics
chosen
Indicates the use or implementation of strategies, maneuvers, or methods intended to protect, guard, or defend against threats or attacks.
-
D.
defender
Indicates a relationship where one entity protects, guards, or supports another entity against threats, attacks, or criticism.
-
E.
typeOfDefense
Indicates the specific kind or category of defense employed or possessed in a given context.
- 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_69a8891b38288190abd572ccad9b6928 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9d239b48190a9f303446cbe3aa6 |
completed | March 7, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69abb7ad5a7c8190b92575d6053b3fb7 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:40 p.m.