Triple
T26946175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yitzhak Kahan |
E678649
|
entity |
| Predicate | commissionChaired |
P129528
|
FINISHED |
| Object | Kahan Commission |
—
|
NE NERFINISHED |
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: Kahan Commission | Statement: [Yitzhak Kahan, commissionChaired, Kahan Commission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commissionChaired Context triple: [Yitzhak Kahan, commissionChaired, Kahan Commission]
-
A.
coChairpersonOf
Indicates that a person serves jointly with one or more others as the chairperson of a group, organization, or committee.
-
B.
chairOfCommission
chosen
Indicates that one entity serves as the chairperson or head of a specific commission associated with another entity.
-
C.
sometimesChairedBy
Indicates that an entity occasionally serves as the chair or leader of another entity, but not on a regular or permanent basis.
-
D.
chairingSystem
Indicates that an entity is responsible for leading, overseeing, or presiding over a particular system or organized structure.
-
E.
chairperson
Indicates that one entity serves as the leader or head of a group, committee, or organization in relation to another entity.
- 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_69eeeb4d69588190a7c912164a1c37b3 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 6:21 a.m.