Triple
T30394446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of the Tiles |
E773174
|
entity |
| Predicate | postDestructionTreatment |
P56983
|
FINISHED |
| Object | covered by tumulus |
—
|
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: covered by tumulus | Statement: [House of the Tiles, postDestructionTreatment, covered by tumulus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postDestructionTreatment Context triple: [House of the Tiles, postDestructionTreatment, covered by tumulus]
-
A.
afterDestruction
chosen
Indicates that one event, state, or condition occurs subsequent to and as a result of a prior act of destruction.
-
B.
postRemovalFunction
Indicates a function or operation that is applied after an item, element, or entity has been removed.
-
C.
afterRemoval
Indicates that a condition, state, or relationship holds only once a specified entity or element has been removed.
-
D.
destroyedDuring
Indicates that one entity was destroyed in the course of, or as a consequence of, a specified event or time period.
-
E.
preDestructionPopulation
Indicates the population size that existed immediately before a destructive event occurred.
- 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_69f2248ef0a48190aa54d4d8ac3e5758 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f685aaa3608190a92f22abfa56ba8a |
completed | May 2, 2026, 11:15 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:02 p.m.