Triple
T2444148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaseman Beckman Advanced Strategies |
E53347
|
entity |
| Predicate | projectSubject |
P33636
|
FINISHED |
| Object | terrorism victims |
—
|
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: terrorism victims | Statement: [Kaseman Beckman Advanced Strategies, projectSubject, terrorism victims]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: projectSubject Context triple: [Kaseman Beckman Advanced Strategies, projectSubject, terrorism victims]
-
A.
subjectOfWork
Indicates that one entity is the main topic, focus, or theme that a particular work (such as a book, article, or artwork) is about.
-
B.
subjectType
Indicates the classification or category that defines what kind of entity the subject is.
-
C.
projectFaced
chosen
Indicates that a project encountered or experienced specific challenges, obstacles, or conditions during its course.
-
D.
subjectMatter
Indicates the topic, theme, or content area that something (such as a work, document, or discussion) is about.
-
E.
subjectCanBe
Indicates that the subject has the potential or capability to assume, become, or be classified as the specified object or state.
- 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_69ab495b6dac8190ac82661aa1452222 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcabf477081908512df63ac1a6414 |
completed | March 7, 2026, 6:50 a.m. |
| PD | Predicate disambiguation | batch_69abc5ad8e588190b97c4cd7cf575043 |
completed | March 7, 2026, 6:29 a.m. |
Created at: March 6, 2026, 9:43 p.m.