Triple
T36513675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thutmose |
E899976
|
entity |
| Predicate | notableArtifactLocation |
P23944
|
FINISHED |
| Object | Neues Museum, Berlin |
E95558
|
NE 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: Neues Museum, Berlin | Statement: [Thutmose, notableArtifactLocation, Neues Museum, Berlin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableArtifactLocation Context triple: [Thutmose, notableArtifactLocation, Neues Museum, Berlin]
-
A.
notableCollectionLocation
chosen
Indicates the place where a notable collection of items, works, or artifacts is held or housed.
-
B.
notableLocation
Indicates that a location is especially significant, prominent, or noteworthy in relation to the subject.
-
C.
notableLocationOn
Indicates that a particular location is especially significant or noteworthy in relation to a specified entity or context.
-
D.
notableEditionLocation
Indicates the place where a particularly significant or notable edition of a work was produced, published, or is held.
-
E.
notablePropertyLocation
Indicates that a specific property or characteristic of an entity is notably associated with, or located in, a particular place.
- F. None of above.
Provenance (4 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_69f76e5dada881909da2d34bc7a9202a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3a094999388190a430011d5c4bb8b7 |
completed | June 23, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.