Triple
T28996639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Location HTTP header |
E736182
|
entity |
| Predicate | mustBeAbsoluteIn |
P83557
|
FINISHED |
| Object | older HTTP specifications |
—
|
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: older HTTP specifications | Statement: [Location HTTP header, mustBeAbsoluteIn, older HTTP specifications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mustBeAbsoluteIn Context triple: [Location HTTP header, mustBeAbsoluteIn, older HTTP specifications]
-
A.
regardsAsAbsolute
Indicates that one entity considers another entity or principle to be unquestionable, ultimate, or not subject to further evaluation or comparison.
-
B.
mustBeUsed
Indicates that one entity is required or obligated to be utilized or applied in relation to another entity or context.
-
C.
isRelativeTo
Indicates that one entity has a familial or kinship relationship to another entity.
-
D.
mustMeet
Indicates that one entity is required or obligated to have a meeting or encounter with another entity.
-
E.
isMandatoryIn
chosen
Indicates that the presence or inclusion of one entity is required or compulsory within the context, scope, or configuration of another entity.
- 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_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:31 a.m.