Triple
T14279599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Τροιζήν |
E354008
|
entity |
| Predicate | modernName |
P1213
|
FINISHED |
| Object | Trizina |
E354009
|
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: Trizina | Statement: [Τροιζήν, modernName, Trizina]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Trizina Context triple: [Τροιζήν, modernName, Trizina]
-
A.
Trizina
chosen
Trizina is a modern Greek settlement located near the ancient city of Troezen in the northeastern Peloponnese.
-
B.
Troistín
Troistín is the Irish-language name for Trostan, the highest mountain in County Antrim, Northern Ireland.
-
C.
Trilistnika
Trilistnika is one of Bulgaria’s Seven Rila Lakes, a high-altitude glacial lake in the Rila Mountains known for its distinctive clover-like shape.
-
D.
Tribeni
Tribeni is a town in West Bengal, India, historically known as a sacred confluence point of rivers and an important riverside settlement.
-
E.
Trisaia
Trisaia is an ENEA research center site in southern Italy known for its activities in energy, environmental, and nuclear technology research.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6585270c8190a717127b2f5dab3b |
completed | April 14, 2026, 4:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd32719ecc8190b57aad5197521359 |
completed | May 8, 2026, 12:46 a.m. |
Created at: April 10, 2026, 1:10 a.m.