Triple
T23312939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ebXML |
E590629
|
entity |
| Predicate | uses |
P98
|
FINISHED |
| Object | MIME |
—
|
NE NERFINISHED |
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: MIME | Statement: [ebXML, uses, MIME]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MIME Context triple: [ebXML, uses, MIME]
-
A.
MIME
chosen
MIME (Multipurpose Internet Mail Extensions) is an internet standard that extends the format of email to support text in character sets beyond ASCII, as well as attachments like images, audio, video, and application files.
-
B.
RFC 2046
RFC 2046 is an Internet standard that defines the structure and types of media content used in the Multipurpose Internet Mail Extensions (MIME) framework.
-
C.
RFC 2045
RFC 2045 is an Internet standard that defines the format and encoding rules for MIME message bodies used in email and related Internet protocols.
-
D.
Multipurpose Internet Mail Extensions
Multipurpose Internet Mail Extensions (MIME) is an Internet standard that extends the format of email to support text in character sets beyond ASCII as well as attachments like images, audio, video, and application files.
-
E.
Message Transfer Part
Message Transfer Part (MTP) is the core lower-layer protocol of the SS7 signaling system that reliably routes and transports signaling messages between network elements in telecommunication networks.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e25d1d32188190948eb76909d1dcc3 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1972ca70481909e2415c65964210a |
completed | April 29, 2026, 5:29 a.m. |
Created at: April 17, 2026, 5:06 p.m.