Triple
T4444723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Pamvotida |
E96254
|
entity |
| Predicate | hasShore |
P969
|
FINISHED |
| Object | Perama |
E306705
|
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: Perama | Statement: [Lake Pamvotida, hasShore, Perama]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Perama Context triple: [Lake Pamvotida, hasShore, Perama]
-
A.
Perama
chosen
Perama is a coastal suburb and port town in the Athens urban area of Greece, known for its shipyards and maritime industry.
-
B.
Enyo
Enyo is a Greek goddess of war and destruction, often depicted as a close companion and counterpart to the war god Ares.
-
C.
Solin
Solin is a town in Croatia near Split, known as the modern successor to the ancient Roman city of Salona.
-
D.
Vipsania
Vipsania is an ancient Roman feminine praenomen (personal name) used within the gens Vipsania.
-
E.
Apama III
Apama III was a Hellenistic queen of Bithynia and member of the Seleucid royal lineage, known primarily as the wife of King Prusias I.
- 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_69b345415ba481908df738e7174448ba |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b355d00c288190a4f3fec29b5d85b2 |
completed | March 13, 2026, 12:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b613850eb88190b689a632b0e2b374 |
completed | March 15, 2026, 2:03 a.m. |
Created at: March 12, 2026, 11:32 p.m.