Triple
T15147528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Larissa prefecture |
E361852
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former prefecture of Greece |
C28756
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: former prefecture of Greece Context triple: [Larissa prefecture, instanceOf, former prefecture of Greece]
-
A.
autonomous region of Greece
An autonomous region of Greece is a geographically defined area within the Greek state that possesses a special legal status granting it a degree of self-governance distinct from the country’s standard administrative divisions.
-
B.
historical region of Greece
A historical region of Greece is a geographically defined area within the Greek world that is recognized for its distinct cultural, political, or historical identity during a specific period of the past.
-
C.
Greek state
A Greek state is a politically organized community in ancient Greece, typically comprising a city (polis) and its surrounding territory, governed by its own institutions, laws, and citizen body.
-
D.
Latin state in Greece
A Latin state in Greece was a feudal polity established by Western European (Latin) crusaders on former Byzantine territory in Greece following the Fourth Crusade, characterized by Latin Christian rule, Western feudal institutions, and cultural interaction with the local Greek population.
-
E.
administrative division of Greece
chosen
An administrative division of Greece is a territorial unit, such as a region, regional unit, or municipality, established by the Greek state for local governance, administration, and public service organization.
- F. None of above.
Provenance (1 batch)
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_69d85a0759908190b8a051d2e2a1cbe6 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:07 a.m.