Triple
T19222808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | royal necropolis of Aigai |
E480660
|
entity |
| Predicate | majorExcavationsDate |
P135239
|
FINISHED |
| Object | 1977 |
—
|
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: 1977 | Statement: [royal necropolis of Aigai, majorExcavationsDate, 1977]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorExcavationsDate Context triple: [royal necropolis of Aigai, majorExcavationsDate, 1977]
-
A.
majorExcavationsBegan
Indicates that significant archaeological or construction excavation work was initiated at a particular time or for a particular project.
-
B.
majorExcavationEndYear
Indicates the year in which a major excavation activity or project was completed.
-
C.
laterExcavationDate
Indicates that one excavation event occurred at a later date than another excavation event.
-
D.
hasArchaeologicalExcavationsSince
Indicates that archaeological excavations have been conducted at an entity starting from a specified point in time and continuing since then.
-
E.
firstExcavationYear
Indicates the calendar year in which an excavation activity at a given site or object was first carried out.
- 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_69d8e8ccb8f48190ad420098e74fb1db |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fa94aed081909045cfed8edc6039 |
completed | April 20, 2026, 10:06 a.m. |
| PD | Predicate disambiguation | batch_69e4dcfae6f081909cc173cf71a5005c |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4debc39ac81908b7c5ef797046360 |
completed | April 19, 2026, 1:55 p.m. |
Created at: April 10, 2026, 1:24 p.m.