Triple
T10590090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Kentucky University |
E249960
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | EKU |
E249960
|
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: EKU | Statement: [Eastern Kentucky University, shortName, EKU]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: EKU Context triple: [Eastern Kentucky University, shortName, EKU]
-
A.
EKU
chosen
EKU is a public university located in Richmond, Kentucky, known for its programs in education, criminal justice, and liberal arts.
-
B.
UAK
UAK was the temporary currency code used for the Ukrainian karbovanets, a transitional currency of Ukraine in the early 1990s before the introduction of the hryvnia.
-
C.
UoK
UoK is the commonly used abbreviation for the University of Khartoum, a leading public university in Sudan.
-
D.
ESU
ESU is a specialized police emergency response unit that handles high-risk situations such as tactical operations, rescues, and hazardous incidents.
-
E.
ESU
ESU is a public university in Emporia, Kansas, known for its programs in education, business, and liberal arts.
- 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_69d381c9d3d48190a29ee491e1696a0e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5277b66448190b668c47fe6af4f3d |
completed | April 7, 2026, 3:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d94b99b3248190b5eac0e99cb73d4b |
completed | April 10, 2026, 7:12 p.m. |
Created at: April 6, 2026, 12:40 p.m.