Triple
T28996635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Location HTTP header |
E736182
|
entity |
| Predicate | for3xxStatus |
P83560
|
FINISHED |
| Object | indicates redirect target URI |
—
|
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: indicates redirect target URI | Statement: [Location HTTP header, for3xxStatus, indicates redirect target URI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: for3xxStatus Context triple: [Location HTTP header, for3xxStatus, indicates redirect target URI]
-
A.
statusInHTTP3
Indicates the HTTP/3 protocol status or condition associated with a given resource, request, or connection.
-
B.
semanticsWith3xx
chosen
Indicates that one entity is associated with or governed by the semantics or behavioral rules defined by a 3xx-class (redirection) HTTP status code of another entity.
-
C.
worksForStatus
Indicates the employment or work-relationship status between an individual and an organization or employer.
-
D.
definedStatusFor
Indicates that one entity establishes or specifies the status or state assigned to another entity.
-
E.
possibleStatus
Indicates the set of statuses that an entity is allowed or able to assume within a given context.
- 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_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:31 a.m.