Triple
T12028818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Egeria |
E286348
|
entity |
| Predicate | described |
P264
|
FINISHED |
| Object | Edessa |
E46023
|
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: Edessa | Statement: [Egeria, described, Edessa]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Edessa Context triple: [Egeria, described, Edessa]
-
A.
Edessa
chosen
Edessa was an ancient city in Upper Mesopotamia, renowned as a major early center of Syriac Christianity and culture.
-
B.
Edessa
Edessa is a historic city in northern Greece renowned for its picturesque waterfalls and ancient heritage.
-
C.
EDESSA
EDESSA is the company responsible for managing and operating Estadio Cuscatlán, one of the largest and most important football stadiums in El Salvador.
-
D.
Hierapolis
Hierapolis was an ancient Greco-Roman city in Phrygia (modern-day Turkey), known for its hot springs and as an early center of Christianity.
-
E.
Turkmenabat
Turkmenabat is one of the largest cities in Turkmenistan, serving as an important industrial, transport, and cultural center in the country’s east near the border with Uzbekistan.
- 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_69d6ab4669e48190b59246358b0383ab |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903f13ae8819097a5740f7c51df82 |
completed | April 10, 2026, 2:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f61e3cd0648190ac6d5587bd7024a7 |
completed | May 2, 2026, 3:54 p.m. |
Created at: April 8, 2026, 9:47 p.m.