Triple
T38044798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Axiom Space |
E949587
|
entity |
| Predicate | roleOfKam Ghaffarian |
P192695
|
FINISHED |
| Object | co-founder and executive |
—
|
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: co-founder and executive | Statement: [Axiom Space, roleOfKam Ghaffarian, co-founder and executive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOfKam Ghaffarian Context triple: [Axiom Space, roleOfKam Ghaffarian, co-founder and executive]
-
A.
roleInSyriana
Indicates that one entity has a specific role or involvement in the context of "Syriana," such as participation, function, or contribution related to it.
-
B.
roleOfChaimKatzman
Indicates that an entity holds or is associated with the specific role or position attributed to Chaim Katzman.
-
C.
AfghanCommander
Indicates that an entity serves in the role of a military commander associated with Afghanistan.
-
D.
roleOfMichael T. Suffredini
Indicates that a specified role, position, or function is held by Michael T. Suffredini.
-
E.
دور
Indicates that an entity has a role, function, or part to play in relation to another entity or within a particular context or process.
- F. None of above. chosen
Provenance (4 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_69f76eff0bb0819084bc4e63997bd039 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
| PDg | Predicate description generation | batch_69fd231bdd108190900369e07c854e95 |
completed | May 7, 2026, 11:41 p.m. |
Created at: May 3, 2026, 4:20 p.m.