Triple
T15914244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avner Kaufman |
E385928
|
entity |
| Predicate | missionInStory |
P68
|
FINISHED |
| Object | lead covert assassination team |
—
|
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: lead covert assassination team | Statement: [Avner Kaufman, missionInStory, lead covert assassination team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionInStory Context triple: [Avner Kaufman, missionInStory, lead covert assassination team]
-
A.
missionStart
Indicates the point in time or event at which a mission or task officially begins.
-
B.
mission
chosen
Indicates that an entity is assigned or engaged in a specific task, operation, or purpose-directed undertaking.
-
C.
intendedMission
Indicates that one entity is the planned or designated mission, task, or objective associated with another entity.
-
D.
publicMission
Indicates that an entity carries out a mission or activity intended for the general public or serving public interests.
-
E.
segmentMission
Indicates that a specific mission is associated with, assigned to, or carried out within a particular segment or phase.
- 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_69d86da686e4819097cbf3b1fc2d881d |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e172b48b308190bc430b2308cbc75b |
completed | April 16, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69e142cf5c548190a931f7b58144cd31 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:52 a.m.