Triple
T30282162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newburgh Priory |
E770128
|
entity |
| Predicate | religiousHouseType |
P92816
|
FINISHED |
| Object | Augustinian priory |
—
|
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: Augustinian priory | Statement: [Newburgh Priory, religiousHouseType, Augustinian priory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousHouseType Context triple: [Newburgh Priory, religiousHouseType, Augustinian priory]
-
A.
religiousHouse
Indicates that an entity is a religious institution or building used for worship, residence, or activities of a religious community.
-
B.
religiousBuildingInstanceOf
chosen
Indicates that a specific religious building is an instance of a particular class or type of religious building.
-
C.
inReligiousStructure
Indicates that one entity is located within or inside a building or structure used for religious purposes.
-
D.
religiousSiteType
Indicates the specific kind or category of religious site associated with an entity (e.g., church, mosque, temple).
-
E.
traditionalReligionPlace
Indicates that a place is traditionally associated with the practice, worship, or activities of a particular religion.
- 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_69f224868fa8819099127eaf8855a28f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe08d2b2e48190ac7be6d62d4a44a3 |
completed | May 8, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69fe06cd3af08190ae25de0dc0cdd573 |
completed | May 8, 2026, 3:52 p.m. |
Created at: April 29, 2026, 7:45 p.m.