Triple
T30116672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Partido Quisqueyano Demócrata Cristiano |
E765436
|
entity |
| Predicate | usesReligionInPlatform |
P76551
|
FINISHED |
| Object | Christianity |
—
|
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: Christianity | Statement: [Partido Quisqueyano Demócrata Cristiano, usesReligionInPlatform, Christianity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesReligionInPlatform Context triple: [Partido Quisqueyano Demócrata Cristiano, usesReligionInPlatform, Christianity]
-
A.
isUsedByReligion
Indicates that something (such as an object, practice, text, or symbol) is employed or utilized within the context of a particular religion.
-
B.
usedReligionFor
chosen
Indicates that an entity employed religion as a means or tool to achieve some purpose, goal, or effect.
-
C.
hasReligious
Indicates that an entity is associated with, practices, or adheres to a particular religion or religious affiliation.
-
D.
portraysReligionAs
Indicates that one entity represents, depicts, or characterizes a religion in a particular way.
-
E.
isNonReligious
Indicates that an entity does not adhere to, practice, or identify with any religion or religious belief system.
- 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_69f2247716748190ae4f16998f49ddf1 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 29, 2026, 7:12 p.m.