Triple
T5480808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ePDG |
E123461
|
entity |
| Predicate | connectsTo |
P845
|
FINISHED |
| Object | EPC |
E23870
|
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: EPC | Statement: [ePDG, connectsTo, EPC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: EPC Context triple: [ePDG, connectsTo, EPC]
-
A.
EPC
chosen
EPC (Evolved Packet Core) is the all-IP mobile core network architecture defined by 3GPP for 4G LTE systems, enabling high-speed data, voice, and multimedia services.
-
B.
ECP
ECP is a fundamental syntactic constraint in generative grammar that governs where empty categories (such as traces) can appear in sentence structure.
-
C.
ECPD
ECPD is the former name of ABET, the primary U.S. organization responsible for accrediting college and university programs in applied science, computing, engineering, and engineering technology.
-
D.
EPD
EPD is the commonly used acronym for the Environmental Protection Division, a governmental body responsible for enforcing environmental laws and regulations.
-
E.
EPD
EPD is the National Rail station code for Epsom Downs railway station in Surrey, England.
- 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_69bd924a2eb08190b759b23a6eab5e0a |
completed | March 20, 2026, 6:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf7fda8a5c81908832c2d59886d824 |
completed | March 22, 2026, 5:36 a.m. |
Created at: March 20, 2026, 2:09 p.m.