Triple
T9959038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aletes |
E195517
|
entity |
| Predicate | ruledOver |
P1715
|
FINISHED |
| Object | Corinth |
E61494
|
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: Corinth | Statement: [Aletes, ruledOver, Corinth]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Corinth Context triple: [Aletes, ruledOver, Corinth]
-
A.
Corinth
chosen
Corinth was an influential ancient Greek city-state strategically located on the Isthmus of Corinth, known for its wealth, maritime trade, and cultural significance.
-
B.
Corinth
Corinth is a small town and village in Saratoga County, New York, known for its historic paper mills and location along the Hudson River near the Adirondack foothills.
-
C.
Corinth
Corinth is a small unincorporated community located in Coweta County, Georgia, United States.
-
D.
Corinth
Corinth is a suburban city within the Dallas–Fort Worth metropolitan area in Texas, known for its residential communities and proximity to major urban centers.
-
E.
Corinto
Corinto is a major Pacific seaport town in northwestern Nicaragua that serves as one of the country’s principal maritime gateways for trade.
- 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_69ca82eaaa008190a54fa1a9f954b9ad |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb6cec7dc8190bb7e43c82a317707 |
completed | April 2, 2026, 12:22 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d257aa73d4819081f77f8386449905 |
completed | April 5, 2026, 12:38 p.m. |
Created at: March 30, 2026, 8:46 p.m.