Triple
T13245387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lembeek |
E315387
|
entity |
| Predicate | hasLocalReligionTradition |
P24121
|
FINISHED |
| Object | Roman Catholicism |
—
|
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: Roman Catholicism | Statement: [Lembeek, hasLocalReligionTradition, Roman Catholicism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalReligionTradition Context triple: [Lembeek, hasLocalReligionTradition, Roman Catholicism]
-
A.
hasRiteOrTradition
Indicates that an entity is associated with, practices, or observes a particular rite, ritual, or tradition.
-
B.
partOfReligiousTradition
Indicates that one entity belongs to, is included within, or is practiced as a component of a particular religious tradition.
-
C.
hostReligion
Indicates that an entity organizes, accommodates, or provides a venue for a particular religious group, event, or practice.
-
D.
religiousTraditions
chosen
Indicates a relationship where certain religious customs, practices, or belief systems are associated with or observed by an entity.
-
E.
hasReligiousSee
Indicates that one entity serves as the ecclesiastical or religious jurisdiction/seat (see) of another entity.
- 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_69d806b1072881909e46bd212259c5f0 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d5b06148190a44e698bbe5cd529 |
completed | April 10, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69d98bcca7d88190a3e68e99ed3a29e6 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:23 p.m.