Triple
T8364160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epifansky Uyezd |
E197081
|
entity |
| Predicate | hasCapital |
P204
|
FINISHED |
| Object |
Epifan
Epifan is a historic Russian town that once served as the administrative center of Epifansky Uyezd in the Tula Governorate.
|
E727998
|
NE FINISHED |
How this triple was built (4 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: Epifan | Statement: [Epifansky Uyezd, hasCapital, Epifan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Epifan Context triple: [Epifansky Uyezd, hasCapital, Epifan]
-
A.
Epip
Epip is a summer month in the Coptic calendar, roughly corresponding to July in the Gregorian calendar.
-
B.
Epher
Epher is a minor biblical figure traditionally regarded as a descendant of Abraham through Keturah and Midian.
-
C.
Eyke
Eyke is a small rural village and civil parish in Suffolk, England, known for its historic church and countryside setting near the River Deben.
-
D.
Profian
Profian is a technology company focused on confidential computing and secure WebAssembly-based solutions.
-
E.
Escamp
Escamp is a largely residential district in the southwest of The Hague in the Netherlands, known for its post-war housing and diverse population.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Epifan Triple: [Epifansky Uyezd, hasCapital, Epifan]
Generated description
Epifan is a historic Russian town that once served as the administrative center of Epifansky Uyezd in the Tula Governorate.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Epifan Target entity description: Epifan is a historic Russian town that once served as the administrative center of Epifansky Uyezd in the Tula Governorate.
-
A.
Epip
Epip is a summer month in the Coptic calendar, roughly corresponding to July in the Gregorian calendar.
-
B.
Epher
Epher is a minor biblical figure traditionally regarded as a descendant of Abraham through Keturah and Midian.
-
C.
Eyke
Eyke is a small rural village and civil parish in Suffolk, England, known for its historic church and countryside setting near the River Deben.
-
D.
Profian
Profian is a technology company focused on confidential computing and secure WebAssembly-based solutions.
-
E.
Escamp
Escamp is a largely residential district in the southwest of The Hague in the Netherlands, known for its post-war housing and diverse population.
- F. None of above. chosen
Provenance (5 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_69ca82f2dbe48190aba982e75a0d94de |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb808a67f88190849152102bfeb574 |
completed | March 31, 2026, 8:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cdc78497cc8190a88bb5934f31e1f7 |
completed | April 2, 2026, 1:33 a.m. |
| NEDg | Description generation | batch_69cdcc88456c8190ba8613b4cbf40fbb |
completed | April 2, 2026, 1:55 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69cdcd75714881908f0b069a94ee334f |
completed | April 2, 2026, 1:59 a.m. |
Created at: March 30, 2026, 6 p.m.