Triple
T31310937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tullianum |
E798459
|
entity |
| Predicate | eraOfContinuedUse |
P176768
|
FINISHED |
| Object | early Roman Empire |
—
|
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: early Roman Empire | Statement: [Tullianum, eraOfContinuedUse, early Roman Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraOfContinuedUse Context triple: [Tullianum, eraOfContinuedUse, early Roman Empire]
-
A.
continuouslyUsedAs
Indicates that one entity is persistently and repeatedly employed or utilized as another entity or for a particular function over an extended, uninterrupted period.
-
B.
lifetimeUse
Indicates that the relationship or action concerns the total or cumulative extent of use of something over the entire duration of an entity’s existence or observation period.
-
C.
subsequentUse
Indicates that one entity is used, applied, or consumed after another entity in time or sequence.
-
D.
durationOfUse
Indicates the length of time for which something is used or remains in use.
-
E.
usedUntil
Indicates that something remained in use or operation up to a specified time or event, after which it was no longer used.
- F. None of above. chosen
Provenance (4 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_69f224e1932c81908fef14f7b03a10b7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69f6e60109648190947a64ca4ce81a3a |
completed | May 3, 2026, 6:06 a.m. |
Created at: April 29, 2026, 9:15 p.m.