Triple
T29547664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1327 |
E749672
|
entity |
| Predicate | hasApplicationProtocol |
P9964
|
FINISHED |
| Object | RFC 822 |
—
|
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 822 | Statement: [RFC 1327, hasApplicationProtocol, RFC 822]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApplicationProtocol Context triple: [RFC 1327, hasApplicationProtocol, RFC 822]
-
A.
hasProtocol
chosen
Indicates that an entity uses, follows, or is governed by a specified protocol or set of procedural rules.
-
B.
hasSubProtocol
Indicates that one protocol is a component, phase, or specialized part of another, more general protocol.
-
C.
hasFlagProtocol
Indicates that an entity is associated with, governed by, or operates under a specific flag protocol or set of flag-related rules.
-
D.
hasApplicationType
Indicates that an entity is associated with or classified by a specific type or category of application.
-
E.
hasOptionalProtocol
Indicates that an entity may, but is not required to, follow or support a specified protocol.
- 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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: April 28, 2026, 5:09 p.m.