Triple
T25165433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | cult of Hephaestus |
E630159
|
entity |
| Predicate | cultCentersInclude |
P114792
|
FINISHED |
| Object | Lemnos |
—
|
NE NERFINISHED |
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: Lemnos | Statement: [cult of Hephaestus, cultCentersInclude, Lemnos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cultCentersInclude Context triple: [cult of Hephaestus, cultCentersInclude, Lemnos]
-
A.
cultCenterFor
Indicates that a location serves as a primary religious or ritual center dedicated to the worship or veneration of a particular entity.
-
B.
centerOfCultFrom
chosen
Indicates that a location serves as the primary cult center or focal place of worship originating from a particular source or entity.
-
C.
centerOfCult
Indicates that the subject functions as the primary focus or core figure around which a cult is organized or devoted.
-
D.
historicallyImportantCenter
Indicates that a place has served as a significant focal point of historical events, activities, or influence.
-
E.
traditionalCenters
Indicates that certain entities serve as established or customary focal points or hubs for particular activities, practices, or communities.
- 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_69e75a87c9b88190ab60731902a99750 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f46d420c6c8190ae3a7731b4978e6d |
completed | May 1, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 12:16 p.m.