Triple
T32958668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matthew Marks |
E843173
|
entity |
| Predicate | hasEponymousOrganization |
P120417
|
FINISHED |
| Object | Matthew Marks Gallery |
—
|
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: Matthew Marks Gallery | Statement: [Matthew Marks, hasEponymousOrganization, Matthew Marks Gallery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEponymousOrganization Context triple: [Matthew Marks, hasEponymousOrganization, Matthew Marks Gallery]
-
A.
eponymFoundedOrganization
chosen
Indicates that a person, whose name is used as the eponym, founded the specified organization.
-
B.
hasOrganizationFor
Indicates that one entity possesses, is associated with, or is responsible for a particular organization in relation to some context or purpose.
-
C.
hasCompanyNamedAfter
Indicates that one entity has a company whose name is derived from or identical to the other entity.
-
D.
foundedOrganization
Indicates that an entity established or created an organization.
-
E.
organizationFounded
Indicates that an organization was established or created at a specific point in time, often by a particular founder or founding 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_69f3494af2808190ad98cec2f1bc0fe6 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d17799888190a57b3e104bf5da6a |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:21 a.m.