Triple
T6452521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Art Gallery of Windsor |
E139903
|
entity |
| Predicate | hasInstitutionCategory |
P58498
|
FINISHED |
| Object | cultural institution |
—
|
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: cultural institution | Statement: [Art Gallery of Windsor, hasInstitutionCategory, cultural institution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInstitutionCategory Context triple: [Art Gallery of Windsor, hasInstitutionCategory, cultural institution]
-
A.
hasInstitutionalCategory
chosen
Indicates that an entity is classified under a specific institutional type or category within an organizational or institutional framework.
-
B.
hasInstitutions
Indicates that one entity possesses, contains, or is associated with one or more institutions.
-
C.
hasPrimaryInstitutionType
Indicates that an entity’s main or principal institutional classification or category is of a specified type.
-
D.
includesInstitution
Indicates that one entity contains, encompasses, or has as a member a particular institution.
-
E.
hasNotableInstitutionType
Indicates that an entity is associated with, or characterized by, a particular type or category of notable institution.
- 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_69c008b301948190a35854e5284dc822 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c069b62cbc81908b7f1a0dc1ed3e1d |
completed | March 22, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69c0673b44148190aed70084f0ff4992 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:47 p.m.