Triple
T7803407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German Historical Museum |
E180486
|
entity |
| Predicate | extensionOpenedIn |
P79098
|
FINISHED |
| Object | 2003 |
—
|
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: 2003 | Statement: [German Historical Museum, extensionOpenedIn, 2003]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extensionOpenedIn Context triple: [German Historical Museum, extensionOpenedIn, 2003]
-
A.
extensionOpened
Indicates that a software extension has been activated or launched from its previously closed or inactive state.
-
B.
extensionOpenedToMernda
Indicates that a transport or infrastructure extension has been opened or extended to reach Mernda.
-
C.
opensInto
Indicates that one space, structure, or passage directly leads or provides access into another space or area.
-
D.
extensionOpeningPeriod
Indicates the time span during which an extension (such as a facility, service, or feature) is open or available for use.
-
E.
openedIn
Indicates that an entity (such as a business, event, or institution) began operating or was inaugurated in a specific time period or location.
- F. None of above. chosen
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_69ca827e50cc8190a92a733577184938 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf78a6d88819093f83528fe88b182 |
completed | March 30, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cae9111b2481909684a2d4aa4831c2 |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf7855a3c81908b9318f7186fc0c0 |
completed | March 30, 2026, 10:21 p.m. |
Created at: March 30, 2026, 4:34 p.m.