Triple
T14280379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plataea monument group |
E354029
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Greek monument ensemble |
C4932
|
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: ancient Greek monument ensemble Context triple: [Plataea monument group, instanceOf, ancient Greek monument ensemble]
-
A.
ancient Greek sanctuary
An ancient Greek sanctuary is a sacred precinct dedicated to one or more deities, typically containing temples, altars, votive offerings, and ritual spaces where religious ceremonies, festivals, and oracles took place.
-
B.
ancient Greek public building
An ancient Greek public building is a communal structure, such as a temple, stoa, theater, or council house, designed to serve civic, religious, political, or social functions within the polis.
-
C.
ancient building complex
chosen
An ancient building complex is a historically significant group of interconnected or closely situated structures, often serving religious, political, residential, or commercial functions within a past civilization.
-
D.
Mycenaean funerary monument
A Mycenaean funerary monument is an architectural structure, such as a tholos tomb or chamber tomb, built by the Mycenaean civilization to honor and bury elite individuals, often featuring monumental stone construction and rich grave goods.
-
E.
Minoan palace complex
A Minoan palace complex is a large, multi-functional architectural center of Minoan civilization that integrated political, religious, economic, and residential activities within an elaborate, often labyrinthine layout.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:10 a.m.