Triple
T2846669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qutb Minar |
E62998
|
entity |
| Predicate | hasDamageHistory |
P37550
|
FINISHED |
| Object | damaged by earthquakes |
—
|
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: damaged by earthquakes | Statement: [Qutb Minar, hasDamageHistory, damaged by earthquakes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDamageHistory Context triple: [Qutb Minar, hasDamageHistory, damaged by earthquakes]
-
A.
hasFireHistory
Indicates that an entity has experienced one or more fire events in the past.
-
B.
hasHistoryOf
chosen
Indicates that an entity has a documented prior occurrence or background of a specified condition, event, or state.
-
C.
hasTransportHistory
Indicates that there exists a record or sequence of past transportation-related events or movements associated with an entity.
-
D.
hasTransportHistoryAs
Indicates that an entity has a record or log of being transported, characterized or classified in a specific way.
-
E.
hasDam
Indicates that a watercourse, reservoir, or similar feature is impounded or controlled by a specific dam.
- 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_69ab4c407c408190857d25e027155ce9 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf3ebbac819090e2bf98ed9fbd02 |
completed | March 7, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_69abdd0e86808190bcefffafbd3cd441 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.