Triple
T10157841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 959 |
E233815
|
entity |
| Predicate | definesReplyCodeRange |
P33257
|
FINISHED |
| Object | 1xx |
—
|
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: 1xx | Statement: [RFC 959, definesReplyCodeRange, 1xx]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesReplyCodeRange Context triple: [RFC 959, definesReplyCodeRange, 1xx]
-
A.
unsatisfiableRangeResponseHeader
Indicates that the response header corresponds to a requested byte range that cannot be satisfied, typically because it falls outside the available representation.
-
B.
usesResponseCode
chosen
Indicates that one entity produces, returns, or relies on a particular response code as part of its behavior or interaction.
-
C.
postalCodeRange
Indicates that one entity specifies a contiguous range of postal codes applicable to another entity or context.
-
D.
hasRange
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
E.
usesCodeUnitRange
Indicates that one entity operates on or is defined in terms of a specific range of code units (e.g., character or byte positions) within another entity.
- 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_69ca848e80748190b91d1e04d35512c7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec5507f08190b47f797bacd5640c |
completed | April 2, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba795808190acc9124c98c6e40f |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:09 p.m.