Triple
T34955374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MDL |
E1008109
|
entity |
| Predicate | developedForInstitution |
P102998
|
FINISHED |
| Object | MIT AI Lab researchers |
—
|
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: MIT AI Lab researchers | Statement: [MDL, developedForInstitution, MIT AI Lab researchers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedForInstitution Context triple: [MDL, developedForInstitution, MIT AI Lab researchers]
-
A.
developedByInstitution
Indicates that something (such as a product, method, or work) was created, produced, or brought into existence by an institution.
-
B.
designedForInstitution
chosen
Indicates that something was specifically created, intended, or tailored to be used by or within a particular institution.
-
C.
developedInstitution
Indicates that an entity played a primary role in creating, establishing, or significantly advancing an institution.
-
D.
establishedInstitution
Indicates that an entity founded, created, or formally set up an institution or organization.
-
E.
servesInstitution
Indicates that one entity provides services or functions in support of a particular institution.
- 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_69f76dc69564819099e9e78aed6ff0a6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: May 3, 2026, 4 p.m.