Triple
T27612134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 7888 |
E700351
|
entity |
| Predicate | usesBCP14Keywords |
P80194
|
FINISHED |
| Object | RFC 2119 |
—
|
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 2119 | Statement: [RFC 7888, usesBCP14Keywords, RFC 2119]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesBCP14Keywords Context triple: [RFC 7888, usesBCP14Keywords, RFC 2119]
-
A.
hasBCPKeyword
chosen
Indicates that an entity is associated with, labeled by, or contains a specific BCP (Business Continuity Plan) keyword.
-
B.
registeredWithIANA
Indicates that an entity is officially recorded and recognized by the Internet Assigned Numbers Authority (IANA) in its registries.
-
C.
hasDNSLabel
Indicates that an entity is associated with, or identified by, a specific DNS label (a name component within the Domain Name System).
-
D.
ICAOCompliant
Indicates that something adheres to the standards and regulations set by the International Civil Aviation Organization (ICAO).
-
E.
followsIANAZone
Indicates that one entity adopts or conforms to the time zone definition specified by the corresponding IANA time zone identifier of another 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 27, 2026, 2:11 p.m.