Triple
T26581461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elliott (namesake of the Elliott Professorship of Sociology) |
E667089
|
entity |
| Predicate | hasNameInChairTitle |
P145831
|
FINISHED |
| Object | "Elliott" |
—
|
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: "Elliott" | Statement: [Elliott (namesake of the Elliott Professorship of Sociology), hasNameInChairTitle, "Elliott"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameInChairTitle Context triple: [Elliott (namesake of the Elliott Professorship of Sociology), hasNameInChairTitle, "Elliott"]
-
A.
hasSeatTitle
Indicates that an entity holds a position or seat identified by a specific title.
-
B.
hasChairmanTitle
Indicates that an entity holds the position or official title of chairman in relation to another entity or organization.
-
C.
namedChairAt
Indicates that a person holds a specific named chair or endowed professorship position at an institution.
-
D.
hasGivenNameInTitle
chosen
Indicates that the given name of an entity appears within the title of another entity.
-
E.
hasCoordinatorTitle
Indicates that an entity holds a role or position specifically designated as a coordinator, as expressed by its title.
- 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_69ee9cfb7e548190b60a9031182f5a7e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 27, 2026, 2:03 a.m.