Triple
T22176938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of Toronto insulin research team |
E548073
|
entity |
| Predicate | timePeriodOfKeyDiscovery |
P26767
|
FINISHED |
| Object | 1921 |
—
|
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: 1921 | Statement: [University of Toronto insulin research team, timePeriodOfKeyDiscovery, 1921]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodOfKeyDiscovery Context triple: [University of Toronto insulin research team, timePeriodOfKeyDiscovery, 1921]
-
A.
hasDiscoveryPeriod
chosen
Indicates the time span during which a particular discovery was made or recognized.
-
B.
discoveredSince
Indicates that one entity has been discovered starting from, or at some point after, a specified time or event associated with another entity.
-
C.
timeGapBetweenCreationAndDiscovery
Indicates the length of time that passes between when something is created and when it is discovered.
-
D.
remainsDiscoveredOn
Indicates that the physical remains of an entity were found or uncovered at a particular location or site.
-
E.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
- 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_69e11e3d53f88190a2b690e3f25bb062 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12a6d03488190b29872ff3f436237 |
completed | April 28, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69e71b41555881909b8e22718974d527 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:34 p.m.