Triple
T31077709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vicus Caprarius |
E792010
|
entity |
| Predicate | chronologyModification |
P88531
|
FINISHED |
| Object | Hadrianic period |
—
|
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: Hadrianic period | Statement: [Vicus Caprarius, chronologyModification, Hadrianic period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologyModification Context triple: [Vicus Caprarius, chronologyModification, Hadrianic period]
-
A.
historicalModification
Indicates that one entity has altered, updated, or otherwise changed another entity at some point in the past, with the modification recorded as part of its history.
-
B.
chronologyNote
Indicates a note that explains or clarifies the temporal order, dating, or sequence of related events or records.
-
C.
changesTimeline
Indicates that one entity alters, restructures, or otherwise affects the sequence or scheduling of events associated with another entity.
-
D.
chronologyType
chosen
Indicates the type or system of chronological ordering or dating applied to an event, period, or sequence.
-
E.
chronologyOf
Indicates that one entity represents the temporal ordering, sequence, or historical timeline of events or states associated with 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: April 29, 2026, 9:02 p.m.