Triple
T5479059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IP |
E123425
|
entity |
| Predicate | usedBy |
P260
|
FINISHED |
| Object | ICMP |
E5619
|
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: ICMP | Statement: [IP, usedBy, ICMP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ICMP Context triple: [IP, usedBy, ICMP]
-
A.
ICMP
ICMP is an international organization that works to locate and identify missing persons and support justice and reconciliation efforts worldwide.
-
B.
ICMP
chosen
ICMP (Internet Control Message Protocol) is a core network-layer protocol used primarily for sending error messages and operational information, such as in tools like ping and traceroute, within IP networks.
-
C.
TCP/IP
TCP/IP is the fundamental communication protocol suite that enables data transmission and networking across the internet and most modern computer networks.
-
D.
Internet Protocol
Internet Protocol is the core networking protocol that defines how data packets are addressed and routed across interconnected computer networks, forming the foundation of the modern internet.
-
E.
Transmission Control Protocol
Transmission Control Protocol is a core internet communication protocol that provides reliable, ordered, and error-checked delivery of data between applications over IP networks.
- 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9247a16c8190ac5a02534da48853 |
completed | March 20, 2026, 6:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf48a001c081909b0e9f1b36fd10db |
completed | March 22, 2026, 1:40 a.m. |
Created at: March 20, 2026, 2:09 p.m.