Triple
T22204372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bechtler family |
E548765
|
entity |
| Predicate | knownForCollection |
P37314
|
FINISHED |
| Object | 20th-century modern art |
—
|
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: 20th-century modern art | Statement: [Bechtler family, knownForCollection, 20th-century modern art]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownForCollection Context triple: [Bechtler family, knownForCollection, 20th-century modern art]
-
A.
knownForCollectionOf
chosen
Indicates that one entity is recognized or notable specifically for its collection or assemblage of another type of entity.
-
B.
namedForKnownFor
Indicates that one entity is named after another entity specifically because that other entity is notable or recognized for something.
-
C.
knownIn
Indicates that an entity is recognized, acknowledged, or familiar within a particular context, domain, or group.
-
D.
segmentKnownFor
Indicates that a specific segment or portion of something is recognized or notable for a particular characteristic, feature, or association.
-
E.
nowKnownFor
Indicates that an entity is currently recognized or notable for a particular role, attribute, achievement, or association.
- 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_69e11e3ecc7c8190b5f94cd8f42e9d37 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12b27451081908c29d1915b6c4229 |
completed | April 28, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69e71b4dcc408190a30429fb08fcf39e |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:36 p.m.