Triple
T17038519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Satricum |
E413381
|
entity |
| Predicate | wasDestroyedMultipleTimes |
P85850
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Satricum, wasDestroyedMultipleTimes, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasDestroyedMultipleTimes Context triple: [Satricum, wasDestroyedMultipleTimes, true]
-
A.
destroyedMultipleTimes
chosen
Indicates that the same entity has been destroyed on more than one distinct occasion.
-
B.
wasDestroyedOrTransformed
Indicates that an entity ceased to exist in its original form due to being either destroyed or fundamentally transformed.
-
C.
rebuiltMultipleTimes
Indicates that the same entity has been reconstructed or restored on more than one separate occasion.
-
D.
destroyedDuring
Indicates that one entity was destroyed in the course of, or as a consequence of, a specified event or time period.
-
E.
diesMultipleTimes
Indicates that the same entity undergoes the event of dying on more than one distinct occasion.
- 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_69d886cd18288190b006abab23f811b7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d8f45f84819092cfb27cc33da026 |
completed | April 18, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69e35d60a588819084f53ef9f8b2e7c0 |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:33 a.m.