Triple
T28936833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of Aphrodite (Aphrodisias) |
E730340
|
entity |
| Predicate | periodOfUseAsPaganTemple |
P169660
|
FINISHED |
| Object | Hellenistic to late Roman 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: Hellenistic to late Roman period | Statement: [Temple of Aphrodite (Aphrodisias), periodOfUseAsPaganTemple, Hellenistic to late Roman period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: periodOfUseAsPaganTemple Context triple: [Temple of Aphrodite (Aphrodisias), periodOfUseAsPaganTemple, Hellenistic to late Roman period]
-
A.
templeUse
Indicates that something is used as, functions as, or serves the purpose of a temple.
-
B.
foundedAsTempleInYear
Indicates that an entity was originally established as a temple in a specific year.
-
C.
hasTemplePurpose
Indicates that something (such as a building, site, or structure) is intended, used, or designated for temple-related purposes or functions.
-
D.
isInUseForWorship
Indicates that something is currently being used for religious or worship-related activities.
-
E.
foundedAsReligiousSiteInCentury
Indicates that something was originally established as a religious site during a specified century.
- 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_69f043ea0aa88190a25acbf46157995a |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f68048391c8190abe6580678f8a9ef |
completed | May 2, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f7e116c819099aec724e9ef3763 |
completed | May 2, 2026, 10:49 p.m. |
Created at: April 28, 2026, 8:33 a.m.