Triple
T37083878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Les Mystères du Château de Dé (patronage) |
E918228
|
entity |
| Predicate | patronRole |
P187474
|
FINISHED |
| Object | art patron |
—
|
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: art patron | Statement: [Les Mystères du Château de Dé (patronage), patronRole, art patron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patronRole Context triple: [Les Mystères du Château de Dé (patronage), patronRole, art patron]
-
A.
patronType
Indicates the classification or category of a patron in relation to a service, institution, or resource.
-
B.
coPatron
Indicates a relationship where two or more entities share joint responsibility or role as patrons supporting the same person, group, or endeavor.
-
C.
primaryPatron
Indicates that one entity serves as the main or chief supporter, sponsor, or benefactor of another entity.
-
D.
typeOfPatronage
Indicates the specific kind or category of support, sponsorship, or backing that one entity provides to another.
-
E.
patron of
Indicates a supportive relationship in which one entity provides sponsorship, protection, or backing to another, often enabling its activities or development.
- 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_69f76e9952b88190a6fe01ba01476520 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69fb55dc36d08190a0634fa680e13114 |
completed | May 6, 2026, 2:53 p.m. |
Created at: May 3, 2026, 4:14 p.m.