Triple
T12962328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacopampa |
E321174
|
entity |
| Predicate | dateOfFirstConstruction |
P96
|
FINISHED |
| Object | around 1200 BCE |
—
|
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: around 1200 BCE | Statement: [Pacopampa, dateOfFirstConstruction, around 1200 BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfFirstConstruction Context triple: [Pacopampa, dateOfFirstConstruction, around 1200 BCE]
-
A.
constructionDate
Indicates the date on which an entity (such as a building or structure) was constructed or completed.
-
B.
dateOfCanonicalErection
Indicates the official date on which an institution, organization, or entity was formally and canonically established or erected according to relevant legal or religious norms.
-
C.
predecessorBuildingDate
Indicates that one building’s construction date precedes that of another building in a temporal sequence.
-
D.
earliestMajorConstruction
Indicates the earliest significant construction event associated with an entity, such as the first major building or development work completed for it.
-
E.
wasFirstBuiltInYear
chosen
Indicates that the initial construction of an entity was completed in a specified year.
- 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_69d80763bd6c819094437da5b20b01d2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97dba57988190b786ffed55687a72 |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:17 p.m.