Triple
T12673357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arg of Karim Khan |
E302741
|
entity |
| Predicate | defensiveFunction |
P48202
|
FINISHED |
| Object | city stronghold |
—
|
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: city stronghold | Statement: [Arg of Karim Khan, defensiveFunction, city stronghold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defensiveFunction Context triple: [Arg of Karim Khan, defensiveFunction, city stronghold]
-
A.
defensiveTask
Indicates a task in which an entity protects, guards, or defends another entity or resource from potential threats or harm.
-
B.
defensiveSystem
chosen
Indicates a system or mechanism whose primary function is to protect, guard, or defend an entity against threats or attacks.
-
C.
defensivePlan
Indicates a relationship where an entity formulates or adopts a strategy specifically intended to protect against threats, attacks, or other adverse actions.
-
D.
defends
Indicates that one entity protects or supports another entity against attack, criticism, or harm.
-
E.
defensiveOperation
Indicates actions or measures undertaken to protect, guard, or defend a target against threats or attacks.
- 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_69d7bdee64a08190801c6d470aefd723 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961af991c8190b6079cb57e593b8f |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960bb64ec8190bd0400cf0cc8b0a7 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:20 p.m.