Triple
T1791650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Zimbabwe |
E39507
|
entity |
| Predicate | excavationYear |
P31970
|
FINISHED |
| Object | 1929 |
—
|
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: 1929 | Statement: [Great Zimbabwe, excavationYear, 1929]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: excavationYear Context triple: [Great Zimbabwe, excavationYear, 1929]
-
A.
excavatedAt
Indicates that an excavation activity took place at a specific location or site.
-
B.
estimatedYearOfCreation
Indicates the year in which something is believed or approximated to have been created, rather than a precisely known creation year.
-
C.
excavatedFrom
Indicates that something (typically an artifact, fossil, or material) was dug out or uncovered from a specific location or source through excavation.
-
D.
excavatedBy
Indicates that something (typically an archaeological site, artifact, or geological feature) was uncovered or dug out by a particular agent (such as a person, team, or organization).
-
E.
reconstructionYear
Indicates the year in which something was rebuilt, restored, or reconstructed after damage, alteration, or destruction.
- 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_69a88631854081909723959921e45c2b |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab61b6ea188190aab9fb839bf1e367 |
completed | March 6, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69aa61d2f7a8819090301f92d3e358c7 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69ab61b5c8988190bb2b46182a4eb5b4 |
completed | March 6, 2026, 11:22 p.m. |
Created at: March 4, 2026, 7:32 p.m.