Triple
T31259940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of Athena (Paestum) |
E797088
|
entity |
| Predicate | usedInRomanPeriodAs |
P72779
|
FINISHED |
| Object | place of worship |
—
|
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: place of worship | Statement: [Temple of Athena (Paestum), usedInRomanPeriodAs, place of worship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInRomanPeriodAs Context triple: [Temple of Athena (Paestum), usedInRomanPeriodAs, place of worship]
-
A.
usedInRomanPeriodFor
chosen
Indicates that something served a particular function, purpose, or application during the Roman period.
-
B.
underRomanRule
Indicates that one entity was politically controlled or governed by the Roman state or its authorities.
-
C.
usesRomanNumerals
Indicates that something represents numbers or sequences using the Roman numeral system rather than standard Arabic digits.
-
D.
usedInLateAntiquity
Indicates that something was in use or actively employed during the historical period of Late Antiquity.
-
E.
yearInRomanHistory
Indicates that a specific year is notable or relevant within the context of Roman history.
- 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_69f224dd5fdc81908a4cd24917b67668 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
Created at: April 29, 2026, 9:12 p.m.