Triple
T37377321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gugenheim |
E928325
|
entity |
| Predicate | isHistoricallyDocumentedIn |
P150962
|
FINISHED |
| Object | 19th century Europe |
—
|
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: 19th century Europe | Statement: [Gugenheim, isHistoricallyDocumentedIn, 19th century Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHistoricallyDocumentedIn Context triple: [Gugenheim, isHistoricallyDocumentedIn, 19th century Europe]
-
A.
historicallyDocumentedBy
Indicates that information about an entity or event is recorded or attested in a specific historical document or source.
-
B.
namedInHistoricalSources
chosen
Indicates that an entity is explicitly mentioned or identified in historical documents or records.
-
C.
legacyDocumentedBy
Indicates that information about a legacy item or concept is recorded or described in a specific documenting source.
-
D.
isHistoricExampleOf
Indicates that something serves as a notable past instance or case that exemplifies or illustrates a particular type, concept, or phenomenon.
-
E.
historicallyGivenIn
Indicates that something was customarily or traditionally granted, presented, or assigned to something or someone in the past.
- 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_69f76eb9e66881908534cf22d04c3b5a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:16 p.m.