Triple
T25652778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tanagra archaeological site |
E643145
|
entity |
| Predicate | regionDuringAntiquity |
P172754
|
FINISHED |
| Object | Boeotia |
—
|
NE NERFINISHED |
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: Boeotia | Statement: [Tanagra archaeological site, regionDuringAntiquity, Boeotia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionDuringAntiquity Context triple: [Tanagra archaeological site, regionDuringAntiquity, Boeotia]
-
A.
countryDuringAntiquity
Indicates that an entity functioned as a country or political territory specifically during the historical period of antiquity.
-
B.
laterRegionInAntiquity
Indicates that one region existed or was defined later in antiquity than another region, reflecting a temporal succession between them.
-
C.
regionDuringEmpire
Indicates that a region existed within or was governed by a particular empire during a specified historical period.
-
D.
ancientStates
Indicates that the related entity functioned as a state or political entity in ancient times.
-
E.
discoveredInAntiquity
Indicates that something was found, identified, or recognized during ancient historical times rather than in the modern era.
- F. None of above. chosen
Provenance (4 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_69e77e7d8a848190a98d0162325fd780 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6b0d21dd08190a9883ff71c94c71c |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6afeaaef88190aefa97e83f8db906 |
completed | May 3, 2026, 2:16 a.m. |
Created at: April 21, 2026, 6:27 p.m.