Triple
T21029277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Θήβα |
E518021
|
entity |
| Predicate | έχει_αρχαιολογικό_χώρο |
P108844
|
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.
hasArchaeologicalSiteIn
chosen
Indicates that an entity possesses, contains, or is associated with an archaeological site located within a specified place or region.
-
B.
hasArchaeologicalSitesFrom
Indicates that an entity contains or is associated with archaeological sites dating from a specified time period or era.
-
C.
isArchaeologicalSite
Indicates that a location or structure is recognized as an archaeological site, typically due to its historical or cultural remains of past human activity.
-
D.
hasArchaeologicalFeature
Indicates that an entity possesses, contains, or is associated with a specific archaeological feature or structure.
-
E.
hasArchaeologicalMuseum
Indicates that an entity possesses or hosts an archaeological museum as part of its features or facilities.
- 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.