Triple
T16631921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santa Pudenziana |
E404099
|
entity |
| Predicate | apseMosaicDate |
P123645
|
FINISHED |
| Object | late 4th century |
—
|
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: late 4th century | Statement: [Santa Pudenziana, apseMosaicDate, late 4th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: apseMosaicDate Context triple: [Santa Pudenziana, apseMosaicDate, late 4th century]
-
A.
movementDate
Indicates the date on which a movement, transfer, or relocation event occurs.
-
B.
dateObserved
Indicates the specific date on which an event, condition, or measurement was recorded or observed.
-
C.
reenvisionedDate
Indicates the date on which something was newly reimagined, redesigned, or conceptually revised.
-
D.
visionDate
Indicates the date on which a particular vision, plan, or conceptual idea was created, recorded, or formally established.
-
E.
dateChangesWith
Indicates that the date associated with one entity is altered or updated in conjunction with, or as a result of, a change involving another entity.
- 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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e378e704c08190a28286ac12165ea5 |
completed | April 18, 2026, 12:28 p.m. |
| PD | Predicate disambiguation | batch_69e296ad3f148190af09223dc35b155c |
completed | April 17, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69e2d7fb02f481908885a226c2191231 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:17 a.m.