Triple
T21573568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manat |
E532340
|
entity |
| Predicate | idolDestroyedIn |
P31453
|
FINISHED |
| Object | 7th century |
—
|
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: 7th century | Statement: [Manat, idolDestroyedIn, 7th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: idolDestroyedIn Context triple: [Manat, idolDestroyedIn, 7th century]
-
A.
sufferedDestructionOf
Indicates that one entity experienced damage, ruin, or loss as a result of the destruction of another entity.
-
B.
sufferedDestructionIn
chosen
Indicates that an entity experienced damage, ruin, or devastation during or as part of a specified event or period.
-
C.
locationOfDestruction
Indicates the place where a destruction event occurred or where something was destroyed.
-
D.
shrineDestroyedBy
Indicates that a shrine has been ruined, demolished, or otherwise destroyed as a result of the actions of a specified agent or cause.
-
E.
destroyedFor
Indicates that one entity was ruined, eliminated, or rendered unusable specifically for the benefit, purpose, or objective of another entity.
- 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_69e0c4618bec8190bcb0feb74568cbb1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eee9cef2748190990a81967d49b706 |
completed | April 27, 2026, 4:45 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:30 p.m.