Triple
T26677318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nengone people |
E672497
|
entity |
| Predicate | presentReligion |
P6676
|
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: [Nengone people, presentReligion, Christianity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentReligion Context triple: [Nengone people, presentReligion, Christianity]
-
A.
religionsPresent
chosen
Indicates that one or more religions are present, practiced, or represented in relation to a given entity or context.
-
B.
officialReligion
Indicates that a particular religion is formally recognized and designated as the official or state religion of an entity (such as a country or region).
-
C.
laterReligion
Indicates that one religion or religious affiliation chronologically follows or replaces another for the same entity.
-
D.
hostReligion
Indicates that an entity organizes, accommodates, or provides a venue for a particular religious group, event, or practice.
-
E.
majorReligionCanBe
Indicates that an entity can have a particular major religion as one of its possible primary religious affiliations.
- 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_69eecda13424819092b17942c4edf722 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 27, 2026, 3:17 a.m.