Triple
T23547841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reguliers |
E577953
|
entity |
| Predicate | livesUnder |
P152751
|
FINISHED |
| Object | religious rule |
—
|
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: religious rule | Statement: [Reguliers, livesUnder, religious rule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: livesUnder Context triple: [Reguliers, livesUnder, religious rule]
-
A.
inResidenceAt
Indicates that an entity lives or resides at a particular location or residence.
-
B.
subdivisionOfResidence
Indicates that a residence is located within or is part of a specific smaller administrative or geographic subdivision (such as a neighborhood, district, or ward).
-
C.
residesNear
Indicates that one entity lives or is located in close physical proximity to another entity.
-
D.
residencyAt
Indicates that an entity lives or has an established residence at a particular location or address.
-
E.
houseLocatedIn
Indicates that a house is situated within or belongs to a specific geographic location or area.
- F. None of above. chosen
Provenance (4 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_69e245fa93448190919cb04534560542 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1aecc2af08190aec07cf9126d4e72 |
completed | April 29, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
| PDg | Predicate description generation | batch_69f121cc494081908c987adfcde89b0e |
completed | April 28, 2026, 9:08 p.m. |
Created at: April 17, 2026, 6:11 p.m.