Triple
T35522275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Building: Letters 1960–1975 |
E1026576
|
entity |
| Predicate | notablePersonDocumented |
P20309
|
FINISHED |
| Object | Isaiah Berlin |
E16747
|
NE 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: Isaiah Berlin | Statement: [Building: Letters 1960–1975, notablePersonDocumented, Isaiah Berlin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePersonDocumented Context triple: [Building: Letters 1960–1975, notablePersonDocumented, Isaiah Berlin]
-
A.
notablePublicFigure
Indicates that the subject is widely recognized and holds a significant public profile or influence in society.
-
B.
notablePersonDiscussed
chosen
Indicates that the subject entity includes or features a discussion about the referenced notable person.
-
C.
documentedPerson
Indicates that a person is the subject of documentation or records in some source or system.
-
D.
notableIndividuals
Indicates that certain individuals are recognized as particularly important, famous, or influential in relation to something.
-
E.
notableFigureFeatured
Indicates that a notable or prominent individual is highlighted, showcased, or given special attention in the associated context or medium.
- F. None of above.
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_69f76dfe78b081908e2b14cb88dd8c00 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39dbb0e9388190a5f7cef4ca7d8d3a |
completed | June 23, 2026, 1:04 a.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:04 p.m.