Triple
T21224633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 3551 |
E523057
|
entity |
| Predicate | definesPayloadTypeRange |
P8440
|
FINISHED |
| Object | static payload types 0–95 |
—
|
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: static payload types 0–95 | Statement: [RFC 3551, definesPayloadTypeRange, static payload types 0–95]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesPayloadTypeRange Context triple: [RFC 3551, definesPayloadTypeRange, static payload types 0–95]
-
A.
rangeType
Indicates the type or category of values that can appear in the range (output) position of a property or relation.
-
B.
payloadType
chosen
Indicates the kind or category of payload associated with or carried by an entity or action.
-
C.
definesMessageType
Indicates that one entity specifies or determines the message type classification or category for another entity.
-
D.
definesType
Indicates that one entity specifies or establishes the type or classification of another entity.
-
E.
nativeRangeType
Indicates the specific type or classification of the geographic area where an entity naturally occurs or originates.
- 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_69e0b512ad94819087942b2ed925185f |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e734aa82c4819086cef6364619b4e9 |
completed | April 21, 2026, 8:26 a.m. |
| PD | Predicate disambiguation | batch_69e5f60e1a888190ba75e2e900270a4e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:44 p.m.