Triple
T1560575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olympia |
E33311
|
entity |
| Predicate | ancientRegion |
P13711
|
FINISHED |
| Object | Elis |
E71370
|
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: Elis | Statement: [Olympia, ancientRegion, Elis]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Elis Context triple: [Olympia, ancientRegion, Elis]
-
A.
Elis
chosen
Elis was an ancient region in the western Peloponnese of Greece, best known as the administrative center of the Olympic Games held at nearby Olympia.
-
B.
Cecilia
Cecilia is a feminine given name of Latin origin, traditionally associated with Saint Cecilia, the patron saint of music.
-
C.
Elia
Elia is a given name most notably associated with influential film and theatre director Elia Kazan.
-
D.
Elise
Elise is a given name associated with the Austrian-Swedish physicist Lise Meitner, a pioneer in nuclear fission research.
-
E.
Elisa
Elisa is a feminine given name of Hebrew origin, often considered a short form of Elisabeth and used in various languages including Italian, Spanish, and French.
- 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_69a885ef9cf48190b0af0f5ce3d02231 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a90885d6208190b4b7d6ad336d4d16 |
completed | March 5, 2026, 4:37 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad401e12088190b6f0f5b0d8a423cf |
completed | March 8, 2026, 9:23 a.m. |
Created at: March 4, 2026, 7:27 p.m.