Triple
T8486809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Location header |
E200850
|
entity |
| Predicate | isResponseHeader |
P48656
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Location header, isResponseHeader, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isResponseHeader Context triple: [Location header, isResponseHeader, true]
-
A.
wasResponseTo
Indicates that one event, action, or communication occurred as a direct reply or reaction to a preceding event, action, or communication.
-
B.
usesResponseCode
Indicates that one entity produces, returns, or relies on a particular response code as part of its behavior or interaction.
-
C.
includesResponse
Indicates that one entity contains, incorporates, or encompasses another entity as a response or reply.
-
D.
hasCallAndResponseStructure
Indicates that one element initiates a call and another element provides a corresponding response, forming a paired, back-and-forth structural pattern.
-
E.
responseField
chosen
Indicates that a particular piece of information is included as part of a response or output structure.
- 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_69ca831d7b148190a6e32c1de43ab13b |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe53c4d608190a766c0e919a4b96f |
completed | March 31, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69cbd107633c8190a36ba50e07876918 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:13 p.m.