Triple
T3600559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spartan army |
E76243
|
entity |
| Predicate | governedBy |
P46
|
FINISHED |
| Object | ephors |
E212305
|
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: ephors | Statement: [Spartan army, governedBy, ephors]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ephors Context triple: [Spartan army, governedBy, ephors]
-
A.
Ephs
Ephs is the distinctive nickname for the athletic teams representing Williams College in intercollegiate sports.
-
B.
Spartan Ephors
chosen
The Spartan Ephors were a powerful council of five annually elected magistrates in ancient Sparta who shared governance with the kings and oversaw civil, military, and educational affairs.
-
C.
Elphi
Elphi is the popular nickname for Hamburg’s Elbphilharmonie, a striking modern concert hall and architectural landmark on the Elbe River.
-
D.
Epher
Epher is a minor biblical figure traditionally regarded as a descendant of Abraham through Keturah and Midian.
-
E.
Pheres
Pheres is a figure in Greek mythology known as one of the sons of the hero Jason.
- 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_69ad85d93dcc819094fba90cf70f4996 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc1a1e8c48190a28ea3ddfe8c4e54 |
completed | March 8, 2026, 6:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4031a41d08190b8e87c452601a625 |
completed | March 13, 2026, 12:29 p.m. |
Created at: March 8, 2026, 3:22 p.m.