Triple
T31519068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Aldate |
E804154
|
entity |
| Predicate | patronageStatus |
P2320
|
FINISHED |
| Object | local patron saint (traditional) |
—
|
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: local patron saint (traditional) | Statement: [Saint Aldate, patronageStatus, local patron saint (traditional)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patronageStatus Context triple: [Saint Aldate, patronageStatus, local patron saint (traditional)]
-
A.
patronState
Indicates a relationship where one state acts as a protector, sponsor, or dominant supporter of another state or political entity.
-
B.
patronage
chosen
Indicates a relationship where one party supports, sponsors, or protects another, often in exchange for loyalty, services, or influence.
-
C.
patronageFrom
Indicates a relationship where support, sponsorship, or backing is provided to someone or something by a patron.
-
D.
hasPatronageOver
Indicates that one entity serves as a patron, sponsor, or protector for another, exercising support, guidance, or authority over it.
-
E.
patronageStyle
Indicates the manner or characteristic way in which support, sponsorship, or patronage is provided in a relationship.
- 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_69f348cf839c81908657048402f7f97b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 9:54 p.m.