Triple
T36860188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mathematikum |
E910909
|
entity |
| Predicate | hasNumberOfExhibitsApprox |
P5288
|
FINISHED |
| Object | 150 |
—
|
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: 150 | Statement: [Mathematikum, hasNumberOfExhibitsApprox, 150]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfExhibitsApprox Context triple: [Mathematikum, hasNumberOfExhibitsApprox, 150]
-
A.
numberOfExhibits
chosen
Indicates the total count of exhibits associated with a given entity or context.
-
B.
hasExhibits
Indicates that an entity (such as a museum, gallery, or event) displays or presents certain items, artworks, or objects as part of its collection or show.
-
C.
hasExhibitsFrom
Indicates a relationship where one entity (typically a venue or collection) includes or displays exhibits originating from another entity (such as an artist, institution, or location).
-
D.
hasExhibitionsAbout
Indicates that one entity organizes or presents exhibitions whose subject matter concerns another entity.
-
E.
hasInteractiveExhibits
Indicates that something contains exhibits designed for active participation or engagement by the audience.
- 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_69f76e8033d48190a59274f86f13be48 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff1c91bbac8190b84012dee1cb3b2c |
completed | May 9, 2026, 11:37 a.m. |
| PD | Predicate disambiguation | batch_69ff1c23ca508190bb5a435d765b7e53 |
completed | May 9, 2026, 11:36 a.m. |
Created at: May 3, 2026, 4:13 p.m.