Triple
T27582506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4918 |
E699617
|
entity |
| Predicate | definesStatusCode |
P179014
|
FINISHED |
| Object | 207 Multi-Status |
—
|
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: 207 Multi-Status | Statement: [RFC 4918, definesStatusCode, 207 Multi-Status]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesStatusCode Context triple: [RFC 4918, definesStatusCode, 207 Multi-Status]
-
A.
definesStatusCodeClass
Indicates that an entity specifies or determines the classification category to which a particular status code belongs.
-
B.
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.
-
C.
definedStatusFor
Indicates that one entity establishes or specifies the status or state assigned to another entity.
-
D.
recognizesStatus
Indicates that one entity acknowledges or accepts the official status or standing of another entity.
-
E.
isStatusOf
Indicates that a particular status or condition is assigned to, or characterizes, a specific 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_69ef6a4cb8b881909b3a8d630fd89df2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f719cc31ec819099bebcf833b14d76 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69f71995853c8190912025c0e83640c8 |
completed | May 3, 2026, 9:47 a.m. |
Created at: April 27, 2026, 2:03 p.m.