Triple
T15815777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gylippus |
E383472
|
entity |
| Predicate | historicalRegion |
P915
|
FINISHED |
| Object | Lacedaemon |
E56539
|
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: Lacedaemon | Statement: [Gylippus, historicalRegion, Lacedaemon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lacedaemon Context triple: [Gylippus, historicalRegion, Lacedaemon]
-
A.
Sparta
Sparta is a historic village in Elgin County, Ontario, known for its 19th-century heritage buildings and roots as a Quaker settlement.
-
B.
Sparta
Sparta is a budget-oriented AMD Sempron processor core designed for entry-level desktop computing.
-
C.
Sparta
chosen
Sparta was a prominent ancient Greek city-state known for its militaristic society, rigorous citizen training, and dominant land-based army.
-
D.
Argives
The Argives were the inhabitants of the ancient Greek city-state of Argos, often prominent participants in Greek myth and history, including the legendary Trojan War.
-
E.
Athens and Sparta
Athens and Sparta were the two leading city-states of ancient Greece, renowned for their contrasting democratic and militaristic societies and their rivalry during the Peloponnesian War.
- 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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0c4a219508190b8588120ec415ac7 |
completed | April 16, 2026, 11:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffa939b4608190ac411b2f2f61e19e |
completed | May 9, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.