Triple
T22522829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asine |
E556822
|
entity |
| Predicate | majorExcavationStartDate |
P7651
|
FINISHED |
| Object | 1922 |
—
|
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: 1922 | Statement: [Asine, majorExcavationStartDate, 1922]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorExcavationStartDate Context triple: [Asine, majorExcavationStartDate, 1922]
-
A.
majorExcavationsBegan
chosen
Indicates that significant archaeological or construction excavation work was initiated at a particular time or for a particular project.
-
B.
majorExcavationsDate
Indicates the date or time period when significant excavation activities were carried out on an entity.
-
C.
majorExcavationEndYear
Indicates the year in which a major excavation activity or project was completed.
-
D.
laterExcavationDate
Indicates that one excavation event occurred at a later date than another excavation event.
-
E.
laterExcavationProjectStartDate
Indicates that the start date of one excavation project occurs after the start date of another excavation project.
- 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_69e11e5657e881909f16ca58352c50da |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15e338dfc819082e1eeede3805fb9 |
completed | April 29, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69ee625e3b408190a60c759fb0b28fe2 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:50 p.m.