Triple
T31324829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Villa of Tiberius at Sperlonga |
E798853
|
entity |
| Predicate | ownerInAntiquity |
P38867
|
FINISHED |
| Object | Tiberius |
—
|
NE NERFINISHED |
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: Tiberius | Statement: [Villa of Tiberius at Sperlonga, ownerInAntiquity, Tiberius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownerInAntiquity Context triple: [Villa of Tiberius at Sperlonga, ownerInAntiquity, Tiberius]
-
A.
ownerDuringMostOfHistory
Indicates that an entity has been the primary or predominant owner of another entity for the majority of the latter’s historical existence.
-
B.
ownerInMyth
Indicates that one entity is the mythological owner, possessor, or master of another entity within a myth or legend.
-
C.
ancientAttributionBy
Indicates that an entity is credited or assigned to another entity based on ancient or historical sources rather than modern evidence.
-
D.
fellInAntiquity
Indicates that an entity experienced a fall, collapse, or defeat during ancient times.
-
E.
ownerDuringEra
chosen
Indicates that one entity is the owner of another entity specifically during a defined historical period or era.
- 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_69f224e3238c8190b2291f50ea4962cd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 29, 2026, 9:15 p.m.