Triple
T29510554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hephaesteum |
E748635
|
entity |
| Predicate | conversionToChurchCentury |
P4040
|
FINISHED |
| Object | 7th century AD (approximate) |
—
|
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: 7th century AD (approximate) | Statement: [Hephaesteum, conversionToChurchCentury, 7th century AD (approximate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conversionToChurchCentury Context triple: [Hephaesteum, conversionToChurchCentury, 7th century AD (approximate)]
-
A.
convertedInCentury
Indicates that an entity underwent a conversion (e.g., religious, functional, or status change) during a specified century.
-
B.
completionCenturyGregorian
Indicates the century, in the Gregorian calendar system, during which the completion of something occurred.
-
C.
dateToCenturyBCE
Indicates the mapping of a specific calendar date to the century before the Common Era (BCE) in which that date falls.
-
D.
conversionToChristianityCentury
chosen
Indicates the century during which an entity underwent or was associated with a conversion to Christianity.
-
E.
dateInCentury
Indicates that a specific date falls within the time span of a given century.
- 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_69f0bd461c208190bec20bbf24e02cc5 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 28, 2026, 4:32 p.m.