Triple
T37802168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santiago, Agusan del Norte |
E942406
|
entity |
| Predicate | hasPrimaryReligionCountryContext |
P202760
|
FINISHED |
| Object | Christianity |
E348
|
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: Christianity | Statement: [Santiago, Agusan del Norte, hasPrimaryReligionCountryContext, Christianity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryReligionCountryContext Context triple: [Santiago, Agusan del Norte, hasPrimaryReligionCountryContext, Christianity]
-
A.
hasMainReligionContext
chosen
Indicates that one entity serves as the primary religious context, tradition, or framework associated with another entity.
-
B.
countryOfReligiousAffiliation
Indicates the country with which a given religious affiliation is associated or to which it belongs.
-
C.
hasPrimaryReligionComplex
Indicates that an entity is primarily associated with, practices, or is characterized by a particular religion or religious complex.
-
D.
religionInCountry
Indicates that a particular religion is practiced, present, or recognized within a specified country.
-
E.
hasAssociatedReligion
Indicates that an entity is connected with or linked to a particular religion.
- 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_69f76ee6f1f4819091e2cf9c9e6aee19 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40f189c424819097bdb83687fab58c |
completed | June 28, 2026, 10:03 a.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:19 p.m.