Triple
T32498720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 2045 |
E830593
|
entity |
| Predicate | MIMEPart |
P174516
|
FINISHED |
| Object | Part One |
—
|
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: Part One | Statement: [RFC 2045, MIMEPart, Part One]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MIMEPart Context triple: [RFC 2045, MIMEPart, Part One]
-
A.
MIMEName
Indicates the standardized MIME (Multipurpose Internet Mail Extensions) type name associated with a given entity, specifying its media type and subtype for content identification.
-
B.
bodyPartDescription
Indicates that one entity provides a descriptive characterization or details about a specific body part of another entity.
-
C.
bodyPartFound
Indicates that a specific body part has been discovered or identified in a particular context or location.
-
D.
bodyPartPresentedTo
Indicates that one entity intentionally exposes or offers a specific body part to another entity as the focus of an interaction or action.
-
E.
losesBodyPart
Indicates that an entity has a body part removed, detached, or otherwise ceases to possess a specific body part.
- 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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c441b8c88190ade9e43a3cd77f3f |
completed | May 3, 2026, 3:42 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c1b666188190ac43c3011a7df048 |
completed | May 3, 2026, 3:32 a.m. |
Created at: May 1, 2026, 12:59 a.m.