Triple
T32774948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reply-To |
E838173
|
entity |
| Predicate | belongsToHeaderSection |
P111407
|
FINISHED |
| Object | Internet Message Format |
—
|
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: Internet Message Format | Statement: [Reply-To, belongsToHeaderSection, Internet Message Format]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToHeaderSection Context triple: [Reply-To, belongsToHeaderSection, Internet Message Format]
-
A.
belongsToHeader
chosen
Indicates that something is associated with, contained within, or conceptually grouped under a specific header.
-
B.
usesHeaderStructure
Indicates that one entity organizes its content using a defined hierarchy of header elements or levels.
-
C.
usesHeadFrom
Indicates that one entity employs or incorporates the head component of another entity in its structure or function.
-
D.
belongsToBody
Indicates that something is a part of, or under the ownership/authority of, a particular body or organization.
-
E.
appliesToSectionOf
Indicates that something is relevant or applicable specifically to a particular section or subsection of a larger whole.
- 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_69f3493a824c8190938489ba69041d08 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fee335cb08819097e3a0e09d5ebf49 |
completed | May 9, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69fee2c74fd88190acfc045ab07b7f6b |
completed | May 9, 2026, 7:31 a.m. |
Created at: May 1, 2026, 1:13 a.m.