Triple
T21029240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Θήβα |
E518021
|
entity |
| Predicate | περιφερειακή ενότητα |
P121380
|
FINISHED |
| Object | Βοιωτία |
—
|
LITERAL 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: Βοιωτία | Statement: [Θήβα, περιφερειακή ενότητα, Βοιωτία]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: περιφερειακή ενότητα Context triple: [Θήβα, περιφερειακή ενότητα, Βοιωτία]
-
A.
crossesAdministrativeRegionOfGreece
Indicates that one entity passes through or extends across the administrative region of Greece associated with another entity.
-
B.
partOfPeripheryUnit
chosen
Indicates that one entity functions as a peripheral component or subdivision belonging to a larger unit or system.
-
C.
capitalOfRegionalUnit
Indicates that one entity serves as the administrative capital of a specified regional unit.
-
D.
apportionmentUnit
Indicates a relationship where something (such as a resource, cost, or quantity) is divided or allocated according to a specified unit or basis of apportionment.
-
E.
isLocatedBetweenMajorRegionsOfGreece
Indicates that something is geographically situated in an area lying between two or more major regions of Greece.
- F. None of above.
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_69e0b503275c8190afd9a163f997c709 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc7fd3ec81908ac237047f9b0d7a |
completed | April 21, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf274ac81909bbf245627dc8fdc |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:55 p.m.