Triple
T28996641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Location HTTP header |
E736182
|
entity |
| Predicate | processedDuring |
P43883
|
FINISHED |
| Object | redirect handling |
—
|
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: redirect handling | Statement: [Location HTTP header, processedDuring, redirect handling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: processedDuring Context triple: [Location HTTP header, processedDuring, redirect handling]
-
A.
processedTo
Indicates that one entity is transformed or converted into another entity through some processing operation.
-
B.
processingUse
Indicates that one entity uses or applies another entity as part of a processing or transformation activity.
-
C.
executedDuring
chosen
Indicates that an action or event was carried out within the temporal span of another specified event or period.
-
D.
constructedDuring
Indicates that one entity was built or created within the time period defined by another entity or event.
-
E.
processingOrder
Indicates the sequence or priority in which items, tasks, or requests are to be processed or handled.
- 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_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 9:31 a.m.