Triple
T9308716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regio VI Alta Semita |
E223953
|
entity |
| Predicate | wasInUseDuring |
P4341
|
FINISHED |
| Object | 1st century AD |
—
|
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: 1st century AD | Statement: [Regio VI Alta Semita, wasInUseDuring, 1st century AD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasInUseDuring Context triple: [Regio VI Alta Semita, wasInUseDuring, 1st century AD]
-
A.
usedDuring
chosen
Indicates that one entity is employed, applied, or active in the course of another entity’s process, event, or time period.
-
B.
wasOccupiedDuring
Indicates that an entity was under the control, presence, or use of another entity throughout a specified time period.
-
C.
wasInForceDuring
Indicates that a rule, law, agreement, or other normative provision was legally valid and operative throughout a specified time period.
-
D.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
-
E.
ownedDuring
Indicates that one entity possessed or held ownership of another entity for some or all of a specified time interval.
- 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_69ca8424d0f08190831e2e93c6533aeb |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd1daba67c819081d53545d67ef127 |
completed | April 1, 2026, 1:29 p.m. |
| PD | Predicate disambiguation | batch_69cc7a61e9a4819096eb014f3791ef2e |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:37 p.m.