Triple
T29443822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSEC3PARAM |
E746789
|
entity |
| Predicate | wireFormatDefinedIn |
P80182
|
FINISHED |
| Object | RFC 5155 Section 3.2 |
—
|
NE NERFINISHED |
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: RFC 5155 Section 3.2 | Statement: [NSEC3PARAM, wireFormatDefinedIn, RFC 5155 Section 3.2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wireFormatDefinedIn Context triple: [NSEC3PARAM, wireFormatDefinedIn, RFC 5155 Section 3.2]
-
A.
protocolDefined
Indicates that a specific protocol formally specifies or governs the behavior, format, or interaction associated with the related entities.
-
B.
definesFormatFor
chosen
Indicates that one entity specifies or establishes the format or structural pattern to be used by another entity.
-
C.
protocolIdentifierFormat
Indicates how a protocol’s identifier is structured or formatted.
-
D.
hasFormatSpecification
Indicates that something is associated with a particular format definition or specification that describes how it should be structured or represented.
-
E.
serializationFormatFor
Indicates the data serialization format used to encode or represent a given resource or 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_69f0a7a180e48190ae775e40047dbcb5 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66b1f46cc8190aeed9e77976f5cd1 |
completed | May 2, 2026, 9:22 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 3:25 p.m.