Triple
T15002739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Domus Aurea |
E374130
|
entity |
| Predicate | wasBuriedBy |
P35790
|
FINISHED |
| Object | subsequent construction and earthworks |
—
|
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: subsequent construction and earthworks | Statement: [Domus Aurea, wasBuriedBy, subsequent construction and earthworks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasBuriedBy Context triple: [Domus Aurea, wasBuriedBy, subsequent construction and earthworks]
-
A.
isBuriedIn
Indicates that one entity is located beneath the ground or enclosed within another entity, typically as in a grave, tomb, or burial site.
-
B.
fellAndBuried
Indicates that one entity fell and consequently became buried, typically under some material or surface.
-
C.
buriedUnder
chosen
Indicates that one entity is located beneath another entity in such a way that it is covered or concealed by it, as if buried.
-
D.
buriedWith
Indicates that one entity is interred in the same grave, tomb, or burial site as another entity.
-
E.
buriedFor
Indicates that one entity is buried on behalf of, in honor of, or as a memorial for 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7312ae48190bdaf91ecced6657e |
completed | April 15, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69de9a6531a88190acde65199a477350 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:54 a.m.