Triple
T32435214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Templo de Cristo Rey |
E828841
|
entity |
| Predicate | isInhabitedPlaceOfWorship |
P161924
|
FINISHED |
| Object | Pasto |
—
|
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: Pasto | Statement: [Templo de Cristo Rey, isInhabitedPlaceOfWorship, Pasto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInhabitedPlaceOfWorship Context triple: [Templo de Cristo Rey, isInhabitedPlaceOfWorship, Pasto]
-
A.
isPlaceOfWorshipFor
Indicates that a location serves as a site where members of a particular religion or belief system perform worship or religious practices.
-
B.
hasPlaceOfWorship
Indicates that an entity possesses, contains, or is associated with a designated location used for religious or spiritual worship.
-
C.
isMajorReligiousBuildingOf
Indicates that a building serves as the primary or most significant religious structure associated with a particular religious group, institution, or area.
-
D.
isInUseForWorship
Indicates that something is currently being used for religious or worship-related activities.
-
E.
isActivePlaceOfWorship
chosen
Indicates that a place is currently functioning and regularly used as a site for religious worship.
- 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_69f3491bf298819097b610f772d54a6d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c2b48a8c8190a6ba0d2f084078cc |
completed | May 3, 2026, 3:36 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:55 a.m.