Triple
T37186147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pantalica archaeological area |
E921325
|
entity |
| Predicate | hasMainCulture |
P1439
|
FINISHED |
| Object | Sicel culture |
E470476
|
NE 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: Sicel culture | Statement: [Pantalica archaeological area, hasMainCulture, Sicel culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainCulture Context triple: [Pantalica archaeological area, hasMainCulture, Sicel culture]
-
A.
hasMainCult
Indicates that an entity is associated with a primary or predominant cult or religious worship tradition.
-
B.
hasAssociatedCulture
chosen
Indicates that an entity is related to, influenced by, or characterized by a particular culture.
-
C.
hasMainLocale
Indicates that an entity’s primary or default locale (language and regional setting) is a specified locale.
-
D.
hasCulturalCore
Indicates that one entity embodies or provides the central cultural values, practices, or identity that fundamentally define another entity.
-
E.
hasCulturalRoots
Indicates that something originates from, is shaped by, or is deeply connected to particular cultural traditions, practices, or heritage.
- F. None of above.
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_69f76ea250bc819083f28d81de25cd0c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40361150cc8190b7e8dd50324f64a3 |
completed | June 27, 2026, 8:44 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:15 p.m.