Triple
T8008991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 857 |
E186435
|
entity |
| Predicate | protocolOptionCode |
P80538
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [RFC 857, protocolOptionCode, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protocolOptionCode Context triple: [RFC 857, protocolOptionCode, 1]
-
A.
protocolNumber
Indicates the specific identifying number assigned to a protocol that governs or documents an interaction, process, or agreement between entities.
-
B.
protocolName
Indicates the specific communication or interaction protocol used or associated with an entity or connection.
-
C.
protocolRule
Indicates that a specified rule or constraint governs how a protocol should be used, structured, or executed between entities.
-
D.
protocolNumberSpace
Indicates that there is a defined set or range of valid protocol numbers associated with the given protocol or system.
-
E.
protocol
Indicates that one entity defines or follows a specific set of rules or procedures governing how it interacts or communicates with another 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_69ca82abaffc8190ab8af79cdbc31ab3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3d6f76408190a1312369521a187a |
completed | March 31, 2026, 3:20 a.m. |
| PD | Predicate disambiguation | batch_69cb048c9f488190b4fb8917a9c21bc5 |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bcbbc0819094a98e7ffffb7a40 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:19 p.m.