Triple
T9099009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Audit Committee of the MIT Corporation |
E218101
|
entity |
| Predicate | mayEngage |
P34786
|
FINISHED |
| Object | independent external auditors |
—
|
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: independent external auditors | Statement: [Audit Committee of the MIT Corporation, mayEngage, independent external auditors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayEngage Context triple: [Audit Committee of the MIT Corporation, mayEngage, independent external auditors]
-
A.
mayEngageIn
chosen
Indicates that one entity is permitted or authorized to participate in or perform a particular activity or interaction with another entity.
-
B.
mayRequest
Indicates that one entity is permitted or authorized to make a request to another entity or for a particular resource or action.
-
C.
mayEnter
Indicates that one entity is permitted or authorized to enter or access another entity or location.
-
D.
engagementTo
Indicates a formal promise or commitment between two entities to enter into a future partnership or binding relationship.
-
E.
mayMeet
Indicates that one entity is permitted or has the possibility to meet or come together with another entity.
- 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_69ca83d9844081908e561e367fda6d45 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc9710ac04819096b9c8d3399b9c35 |
completed | April 1, 2026, 3:54 a.m. |
| PD | Predicate disambiguation | batch_69cc65fc7f408190a5846e29ab3b97e5 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:15 p.m.