Triple
T16538553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomb of Queen Sitre |
E401758
|
entity |
| Predicate | likelyConstructionDate |
P106367
|
FINISHED |
| Object | reign of Ramesses I |
—
|
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: reign of Ramesses I | Statement: [Tomb of Queen Sitre, likelyConstructionDate, reign of Ramesses I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likelyConstructionDate Context triple: [Tomb of Queen Sitre, likelyConstructionDate, reign of Ramesses I]
-
A.
claimedConstructionDate
Indicates the date on which an entity is asserted or reported to have been constructed, according to some claim or source.
-
B.
constructionDate
Indicates the date on which an entity (such as a building or structure) was constructed or completed.
-
C.
startOfConstructionApprox
chosen
Indicates that the construction of something began around an approximate or estimated point in time, rather than on a precisely known date.
-
D.
associatedBuildingDate
Indicates the date on which a particular building is formally linked or related to another entity or record.
-
E.
laterConstruction
Indicates that one construction event or structure occurred or was built after another in time.
- 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3455a98b481909e489ea7bd01570a |
completed | April 18, 2026, 8:48 a.m. |
| PD | Predicate disambiguation | batch_69e2969fab208190ad64164d24748c45 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:15 a.m.