Triple
T2660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MIT Libraries |
E49
|
entity |
| Predicate | hasDigitalInitiative |
P344
|
FINISHED |
| Object | digital collections |
—
|
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: digital collections | Statement: [MIT Libraries, hasDigitalInitiative, digital collections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDigitalInitiative Context triple: [MIT Libraries, hasDigitalInitiative, digital collections]
-
A.
isAnalogOrDigital
Indicates whether something operates using analog signals/representation or digital signals/representation.
-
B.
hasOnlinePlatform
Indicates that an entity operates, maintains, or is associated with a presence or service on an online platform.
-
C.
developedAt
Indicates the place or location where something was created, built, or developed.
-
D.
hasLegacy
Indicates that an entity leaves behind a lasting impact, influence, or inheritance that continues to exist or be recognized over time.
-
E.
hasTechnicalSociety
Indicates that an entity is associated with, or possesses membership in, a technical or engineering-focused society or organization.
- F. None of above. chosen
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_69a22e0d37588190897cf37a323013f5 |
completed | Feb. 27, 2026, 11:51 p.m. |
| NER | Named-entity recognition | batch_69a2346846608190b6b40d31f1dbd685 |
completed | Feb. 28, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69a233c396ec8190986608d07fb251d4 |
completed | Feb. 28, 2026, 12:16 a.m. |
| PDg | Predicate description generation | batch_69a2346794cc8190afce97b703903389 |
completed | Feb. 28, 2026, 12:18 a.m. |
Created at: Feb. 27, 2026, 11:55 p.m.