Triple
T28996582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Last-Modified |
E736181
|
entity |
| Predicate | headerSection |
P93020
|
FINISHED |
| Object | response header section |
—
|
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: response header section | Statement: [Last-Modified, headerSection, response header section]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headerSection Context triple: [Last-Modified, headerSection, response header section]
-
A.
header
chosen
Indicates that one entity serves as a heading or title section that precedes and organizes the content of another entity.
-
B.
headerCategory
Indicates that one entity serves as a categorical grouping or classification for the header or heading represented by the other entity.
-
C.
headContent
Indicates that one entity serves as the primary or main content contained within another entity.
-
D.
headDescription
Indicates that one entity serves as a textual or semantic description of the head (primary) entity in the relationship.
-
E.
homeSection
Indicates that something belongs to, is part of, or is designated as the primary/home section within a larger structure or collection.
- 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f65fb6ef4881909a758c3538fdec03 |
completed | May 2, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 9:31 a.m.