Triple
T33336171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1847 |
E853541
|
entity |
| Predicate | definesHeaderUsageFor |
P37271
|
FINISHED |
| Object | MIME security multiparts |
—
|
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: MIME security multiparts | Statement: [RFC 1847, definesHeaderUsageFor, MIME security multiparts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesHeaderUsageFor Context triple: [RFC 1847, definesHeaderUsageFor, MIME security multiparts]
-
A.
definesHeader
Indicates that one entity serves as the header or defining heading for another entity.
-
B.
definesUseOf
chosen
Indicates that one entity specifies or determines how another entity is to be used or applied.
-
C.
definitionUses
Indicates that one definition makes use of, depends on, or references another definition.
-
D.
usesHeaderStructure
Indicates that one entity organizes its content using a defined hierarchy of header elements or levels.
-
E.
usesHeadFrom
Indicates that one entity employs or incorporates the head component of another entity in its structure or function.
- 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_69f34969614c81909cd99661b0902533 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe6739d4dc8190ae7505c089bbac29 |
completed | May 8, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69fe6541dffc81909c66a61ba69f38fc |
completed | May 8, 2026, 10:35 p.m. |
Created at: May 1, 2026, 1:34 a.m.