Triple
T8616454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Gallery |
E204050
|
entity |
| Predicate | isCommonlyAssociatedWith |
P2830
|
FINISHED |
| Object | art museums |
—
|
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 museums | Statement: [New Gallery, isCommonlyAssociatedWith, art museums]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCommonlyAssociatedWith Context triple: [New Gallery, isCommonlyAssociatedWith, art museums]
-
A.
isAssociatedWith
chosen
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
B.
isCommonlyDefinedBy
Indicates that something is typically or most frequently characterized, specified, or described by a particular definition, property, or set of criteria.
-
C.
notablyAssociatedWith
Indicates that one entity is prominently or distinctively connected with another in a way that is especially noteworthy or remarkable.
-
D.
associatedWithUse
Indicates a relationship where one entity is connected to or involved in the use or utilization of another entity.
-
E.
isFamouslyUsedIn
Indicates that something is widely recognized or well-known for being used in a particular context, work, or situation.
- 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_69ca832ceab8819096e4a9f546695079 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc4703b57c81909511de72fa5c38d7 |
completed | March 31, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cc455437488190b7506f820daf6e32 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:25 p.m.