Triple
T34232426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamar Rabinyan |
E878235
|
entity |
| Predicate | primaryMissionInSeries |
P38163
|
FINISHED |
| Object | covert operation in Tehran |
—
|
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: covert operation in Tehran | Statement: [Tamar Rabinyan, primaryMissionInSeries, covert operation in Tehran]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryMissionInSeries Context triple: [Tamar Rabinyan, primaryMissionInSeries, covert operation in Tehran]
-
A.
primaryMissions
Indicates the main missions or core objectives assigned to or undertaken by an entity.
-
B.
primaryMissionTo
chosen
Indicates that an entity has a main or principal mission directed toward or focused on another entity.
-
C.
primaryFunctionInSeries
Indicates that an entity serves as the main or most important function within a particular series or sequence.
-
D.
laterPrimaryMission
Indicates that one mission occurs after another mission in the sequence of primary missions.
-
E.
primaryMissionProgram
Indicates that an entity serves as the main or principal program under which another entity’s mission or primary activity is organized or executed.
- 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_69f349b22d8c819096b22df268382aa9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:56 a.m.