Triple

T10104345
Position Surface form Disambiguated ID Type / Status
Subject Content-Range header field E216279 entity
Predicate mustNotAppearWithStatusCode P70622 FINISHED
Object 200 OK 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: 200 OK | Statement: [Content-Range header field, mustNotAppearWithStatusCode, 200 OK]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mustNotAppearWithStatusCode
Context triple: [Content-Range header field, mustNotAppearWithStatusCode, 200 OK]
  • A. usesStatusCodeClass
    Indicates that one entity employs or relies on a particular class or range of status codes (e.g., HTTP status code classes) in its behavior or processing.
  • B. definesStatusCodeClass
    Indicates that an entity specifies or determines the classification category to which a particular status code belongs.
  • C. mustAvoid chosen
    Indicates that one entity is required to stay away from, not engage with, or prevent interaction with another entity or condition.
  • D. doesNotApplyIf
    Indicates that a rule, condition, or effect is not valid or should not be enforced when a specified circumstance or exception is present.
  • E. requiresStatus
    Indicates that one entity can only proceed, be valid, or be applied if another entity has a specified status or condition.
  • 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_69ca83d039f08190b9d10363221c69fb completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cdd09c961081909848acec4438c300 completed April 2, 2026, 2:12 a.m.
PD Predicate disambiguation batch_69cd4b9b853c8190a2af993ce9b21309 completed April 1, 2026, 4:45 p.m.
Created at: March 30, 2026, 9:03 p.m.