Triple
T7928346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MIB-I |
E184123
|
entity |
| Predicate | versionRole |
P79830
|
FINISHED |
| Object | original version of the Internet-standard MIB |
—
|
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: original version of the Internet-standard MIB | Statement: [MIB-I, versionRole, original version of the Internet-standard MIB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: versionRole Context triple: [MIB-I, versionRole, original version of the Internet-standard MIB]
-
A.
unitRole
Indicates the functional role or purpose that a unit serves within a larger system or context.
-
B.
definesRole
Indicates that one entity specifies or establishes the role, function, or position of another entity within a given context.
-
C.
typeOfRole
Indicates that one entity specifies the kind or category of role that another entity holds or performs.
-
D.
revivalVersionRole
Indicates the role or function an entity has in relation to a particular version of a revival (e.g., a new staging, edition, or re-release) of a work or event.
-
E.
configurationRole
Indicates the role or function an entity assumes within a particular configuration or setup.
- 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_69ca828fe7bc819090f52c88dcd72183 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3ac9ac4c819082cd2190fc3ce5a2 |
completed | March 31, 2026, 3:08 a.m. |
| PD | Predicate disambiguation | batch_69cae9335f288190ba96781fd6576a2b |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf7882b048190baa333af9f698590 |
completed | March 30, 2026, 10:22 p.m. |
Created at: March 30, 2026, 5:07 p.m.