Triple
T20968261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vijay Karunamurthy |
E516426
|
entity |
| Predicate | hasLeadershipExperienceIn |
P142295
|
FINISHED |
| Object | major technology companies |
—
|
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: major technology companies | Statement: [Vijay Karunamurthy, hasLeadershipExperienceIn, major technology companies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLeadershipExperienceIn Context triple: [Vijay Karunamurthy, hasLeadershipExperienceIn, major technology companies]
-
A.
governingExperience
Indicates that an entity has experience in governing or exercising authority over others or over an organization, territory, or system.
-
B.
hasLeaderHeldOffice
Indicates that the specified leader has occupied or served in an official office or position.
-
C.
hadLeadershipFrom
Indicates that one entity received leadership, guidance, or direction from another entity.
-
D.
hasLeaderInGovernment
Indicates that one entity serves as the leader or head of government for another entity.
-
E.
hasElectedLeadership
Indicates that an entity possesses leaders who have been chosen through an election or voting 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_69e0b4fee5ac8190875fa9ceba1a5e5e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fb9d6b548190af7214ad2468cfbf |
completed | April 21, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69e5dbe6976081908abd4e9c8734bae9 |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2df1a888190b5b478e76bdf7fdf |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 1:40 p.m.