Triple
T15210776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deinomenid dynasty |
E363507
|
entity |
| Predicate | originCity |
P1041
|
FINISHED |
| Object | Gela |
E55087
|
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: Gela | Statement: [Deinomenid dynasty, originCity, Gela]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gela Context triple: [Deinomenid dynasty, originCity, Gela]
-
A.
Gela
Gela is a river in southern Sicily, Italy, that flows into the Mediterranean Sea near the city of Gela.
-
B.
Gela
Gela is a mountain village in the Rhodope Mountains of southern Bulgaria, known for its scenic landscapes and traditional Bulgarian culture.
-
C.
Gela
chosen
Gela is an ancient Greek colonial city on the southern coast of Sicily that was a significant center of Magna Graecia.
-
D.
Gela
Gela is an Oceanic language spoken primarily in the Solomon Islands, particularly on Nggela (Florida) Islands in Central Province.
-
E.
Leontini
Leontini was an ancient Greek city in eastern Sicily, known as a Chalcidian colony and a frequent player in the island’s classical-era conflicts.
- 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_69d85a0b78bc8190b6e5ad51a2c4cfc5 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0076ad4ec81908d36f541fca08d72 |
completed | April 15, 2026, 9:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fef88f8ac881908ca32de44b5aa53a |
completed | May 9, 2026, 9:04 a.m. |
Created at: April 10, 2026, 3:11 a.m.