Triple
T33819964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert de Vaux |
E866800
|
entity |
| Predicate | religiousPatronageLocation |
P142484
|
FINISHED |
| Object | Norfolk |
—
|
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: Norfolk | Statement: [Robert de Vaux, religiousPatronageLocation, Norfolk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousPatronageLocation Context triple: [Robert de Vaux, religiousPatronageLocation, Norfolk]
-
A.
religiousPatronageIn
chosen
Indicates that an entity provides religious patronage, support, or sponsorship within a specified place or region.
-
B.
saintPatronageAssociatedWith
Indicates that a patronage relationship exists, where a saint is recognized as a special protector or advocate for a particular person, group, place, activity, or cause.
-
C.
mainChurchPatron
Indicates that one entity serves as the primary patron or chief sponsoring supporter of a particular church.
-
D.
veneratedAt
Indicates that an entity is honored, revered, or worshipped at a particular place or institution.
-
E.
locatedInCityWithPatronSaint
Indicates that an entity is situated in a city whose designated patron saint is a specific person.
- 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_69f349911a8c81908478662194b23d8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff3e1762d8819089a60e402e682817 |
completed | May 9, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69ff3d8c6f308190a0646b1432752eb8 |
completed | May 9, 2026, 1:58 p.m. |
Created at: May 1, 2026, 1:46 a.m.