Triple
T7209277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harrington Professor of History |
E148756
|
entity |
| Predicate | isDistinguished |
P12620
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Harrington Professor of History, isDistinguished, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDistinguished Context triple: [Harrington Professor of History, isDistinguished, true]
-
A.
isDistinguishedBy
Indicates that one entity is characterized or set apart from others by a particular feature, quality, or attribute.
-
B.
hasDistinction
chosen
Indicates that one entity possesses, is awarded, or is recognized with a special honor, title, or mark of excellence in relation to another entity or context.
-
C.
hasRegisterDistinction
Indicates that there is a meaningful difference in language register (e.g., formality or style) between the related linguistic forms or usages.
-
D.
isCeremoniallyDistinctFrom
Indicates that two entities are formally separated or differentiated from each other within a ritual, ceremonial, or symbolic context.
-
E.
isDistinctFrom
Indicates that two entities are not identical and can be clearly distinguished from one another.
- 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_69c687e8cf188190b5f3ecffd681f04e |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6e96c46dc819080a6b40456d7b068 |
completed | March 27, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69c6e75f84e481909e7866186ae80cff |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:52 p.m.