Triple
T1632144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internet Standard |
E35278
|
entity |
| Predicate | hasExample |
P1259
|
FINISHED |
| Object | STD 5 |
E60157
|
NE 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: STD 5 | Statement: [Internet Standard, hasExample, STD 5]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: STD 5 Context triple: [Internet Standard, hasExample, STD 5]
-
A.
STD 5
chosen
STD 5 is the Internet Standard that defines the core Internet Protocol (IP), as specified primarily in RFC 791.
-
B.
STD 1
STD 1 is an early Internet Standard that specifies the foundational Internet Protocol (IP), defining how data packets are addressed and routed across interconnected networks.
-
C.
STD 3
STD 3 is an Internet Standard that specifies the core Internet Protocol (IP) used for addressing and routing packets across interconnected networks.
-
D.
STD 68
STD 68 is an Internet Standard that specifies the core Internet Control Message Protocol (ICMP) used for network diagnostics and error reporting in IP networks.
-
E.
STD 90
STD 90 is an Internet Standard that specifies the core Internet Protocol (IP) and related requirements fundamental to interoperable networking on the Internet.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a886036bc081909ff5de16dbe5e8ea |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a909f6ee1881908f0753a77a2c4665 |
completed | March 5, 2026, 4:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad6815c4588190bccfbece8f22c1a1 |
completed | March 8, 2026, 12:14 p.m. |
Created at: March 4, 2026, 7:28 p.m.