Triple
T6272192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herman Feshbach Professor of Physics at MIT |
E140561
|
entity |
| Predicate | namedChairIn |
P64804
|
FINISHED |
| Object | physics |
—
|
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: physics | Statement: [Herman Feshbach Professor of Physics at MIT, namedChairIn, physics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedChairIn Context triple: [Herman Feshbach Professor of Physics at MIT, namedChairIn, physics]
-
A.
chairDesignationBy
Indicates that an entity holds the role or title of chair as assigned or designated by another entity.
-
B.
chairIn
chosen
Indicates that one entity is a chair located within the spatial bounds or interior of another entity.
-
C.
coChairWith
Indicates that two or more entities share the role of chairing the same group, event, or organization jointly.
-
D.
chairperson
Indicates that one entity serves as the leader or head of a group, committee, or organization in relation to another entity.
-
E.
coChairpersonOf
Indicates that a person serves jointly with one or more others as the chairperson of a group, organization, or committee.
- 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_69c008cabc4081909723e2547c9d6cc0 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063bca5488190b9da3c037cfc7953 |
completed | March 22, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69c05606fb50819082d1a5a91e5030b6 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:25 p.m.