Triple
T25933641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Owen family |
E653494
|
entity |
| Predicate | roleInOwenArtsCenter |
P96020
|
FINISHED |
| Object | namesake benefactor |
—
|
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: namesake benefactor | Statement: [Owen family, roleInOwenArtsCenter, namesake benefactor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInOwenArtsCenter Context triple: [Owen family, roleInOwenArtsCenter, namesake benefactor]
-
A.
exhibitionRole
Indicates the specific function or capacity an entity has within the context of an exhibition (e.g., organizer, curator, exhibitor, or participant).
-
B.
hasExhibitionRole
Indicates that an entity holds a specific role or function within the context of an exhibition.
-
C.
roleInArtScene
chosen
Indicates that an entity holds a particular function, position, or involvement within an artistic or cultural scene.
-
D.
hasCuratorialRole
Indicates that an entity holds a curatorial position or responsibility in relation to another entity, such as overseeing its selection, organization, or presentation.
-
E.
exhibitsWorkOf
Indicates that one entity displays or presents the creative works produced by another entity.
- 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 22, 2026, 8:37 a.m.