Triple
T35902335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Punta Chueca |
E1038385
|
entity |
| Predicate | cultureCenterFor |
P4313
|
FINISHED |
| Object | Seri people |
—
|
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: Seri people | Statement: [Punta Chueca, cultureCenterFor, Seri people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cultureCenterFor Context triple: [Punta Chueca, cultureCenterFor, Seri people]
-
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.
isCulturalCenterFor
chosen
Indicates that one entity serves as a primary hub or focal point for the cultural activities, heritage, or identity of another entity.
-
C.
centerOfCultFrom
Indicates that a location serves as the primary cult center or focal place of worship originating from a particular source or entity.
-
D.
isCulturalCenter
Indicates that an entity serves as a primary hub or focal point for the cultural activities, expressions, and institutions of a community or region.
-
E.
centerOfCult
Indicates that the subject functions as the primary focus or core figure around which a cult is organized or devoted.
- 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_69f76e2190f88190beb2eed798a4ef01 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: May 3, 2026, 4:07 p.m.