Triple
T8692852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 5011 |
E206332
|
entity |
| Predicate | hasProtocolNumber |
P3682
|
FINISHED |
| Object | none |
—
|
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: none | Statement: [RFC 5011, hasProtocolNumber, none]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProtocolNumber Context triple: [RFC 5011, hasProtocolNumber, none]
-
A.
protocolNumber
chosen
Indicates the specific identifying number assigned to a protocol that governs or documents an interaction, process, or agreement between entities.
-
B.
hasProtocol
Indicates that an entity uses, follows, or is governed by a specified protocol or set of procedural rules.
-
C.
protocolNumberSpace
Indicates that there is a defined set or range of valid protocol numbers associated with the given protocol or system.
-
D.
hasFlagProtocol
Indicates that an entity is associated with, governed by, or operates under a specific flag protocol or set of flag-related rules.
-
E.
hasProtocolStatus
Indicates that an entity is associated with a particular protocol-related state or condition it currently holds.
- 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_69ca835481fc819084e33d3bc883bfa6 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5825385081908dee42cba8e98392 |
completed | March 31, 2026, 11:26 p.m. |
| PD | Predicate disambiguation | batch_69cc4569f9048190b9c86b4c81103d35 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:33 p.m.