Triple
T35359405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petrović-Njegoš |
E1021431
|
entity |
| Predicate | hasHouseReligion |
P27867
|
FINISHED |
| Object | Serbian Orthodox Church |
—
|
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: Serbian Orthodox Church | Statement: [Petrović-Njegoš, hasHouseReligion, Serbian Orthodox Church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHouseReligion Context triple: [Petrović-Njegoš, hasHouseReligion, Serbian Orthodox Church]
-
A.
hasFormerReligiousHouse
Indicates that an entity once contained or was associated with a religious house (such as a monastery, convent, or similar institution) that no longer exists or functions in that capacity.
-
B.
hasAssociatedReligion
chosen
Indicates that an entity is connected with or linked to a particular religion.
-
C.
hostReligion
Indicates that an entity organizes, accommodates, or provides a venue for a particular religious group, event, or practice.
-
D.
hasReligious
Indicates that an entity is associated with, practices, or adheres to a particular religion or religious affiliation.
-
E.
hasReligiousOrganization
Indicates that an entity is associated with, governed by, or belongs to a specific religious organization.
- 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_69f76def44c881908a20e8008572eb44 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fdd07a34c08190982b8c61c2775cf6 |
completed | May 8, 2026, noon |
| PD | Predicate disambiguation | batch_69fdbd25c7908190b72fca8de7ce503f |
completed | May 8, 2026, 10:38 a.m. |
Created at: May 3, 2026, 4:03 p.m.