Triple
T28996634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Location HTTP header |
E736182
|
entity |
| Predicate | forStatus201 |
P166101
|
FINISHED |
| Object | identifies newly created resource 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: identifies newly created resource URI | Statement: [Location HTTP header, forStatus201, identifies newly created resource URI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forStatus201 Context triple: [Location HTTP header, forStatus201, identifies newly created resource URI]
-
A.
definedStatusFor
Indicates that one entity establishes or specifies the status or state assigned to another entity.
-
B.
worksForStatus
Indicates the employment or work-relationship status between an individual and an organization or employer.
-
C.
obtainedStatus
Indicates that an entity has received or achieved a particular status or condition as a result of some process or event.
-
D.
post2000Status
Indicates whether a given entity’s status, condition, or classification applies specifically to the period after the year 2000.
-
E.
createsStatus
Indicates that one entity brings about, initiates, or establishes a particular state or condition in another entity.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f65b136b30819090cf59fb772f35f1 |
completed | May 2, 2026, 8:14 p.m. |
Created at: April 28, 2026, 9:31 a.m.