Triple
T27506652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huimanguillo |
E694295
|
entity |
| Predicate | hasSecondaryReligions |
P26280
|
FINISHED |
| Object | various Christian denominations |
—
|
LITERAL 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: various Christian denominations | Statement: [Huimanguillo, hasSecondaryReligions, various Christian denominations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondaryReligions Context triple: [Huimanguillo, hasSecondaryReligions, various Christian denominations]
-
A.
hasSecondaryReligion
chosen
Indicates that an entity practices, adheres to, or is associated with a secondary religion in addition to its primary religion.
-
B.
hasPrimaryReligionComplex
Indicates that an entity is primarily associated with, practices, or is characterized by a particular religion or religious complex.
-
C.
isMultiReligious
Indicates that an entity is associated with or practices multiple religions rather than adhering to just one.
-
D.
hasSecondaryDeity
Indicates that an entity has an associated secondary or subordinate deity linked to it.
-
E.
hasAssociatedReligion
Indicates that an entity is connected with or linked to a particular religion.
- 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_69ef538370888190b1ddf53bb4831188 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: April 27, 2026, 1:13 p.m.