Triple
T30196200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stasi Museum |
E767635
|
entity |
| Predicate | locatedInFormerHeadquartersOf |
P14806
|
FINISHED |
| Object | Stasi |
—
|
NE NERFINISHED |
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: Stasi | Statement: [Stasi Museum, locatedInFormerHeadquartersOf, Stasi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInFormerHeadquartersOf Context triple: [Stasi Museum, locatedInFormerHeadquartersOf, Stasi]
-
A.
wasHeadquartersDuring
Indicates that a particular location served as the headquarters of an entity during a specified time period.
-
B.
headquartersPreviousLocation
Indicates that an entity’s headquarters used to be located at a specified place before moving to its current location.
-
C.
locatedAtFormer
Indicates that an entity is currently located at a place where another entity was previously located.
-
D.
hasMuseumAtFormerHQ
chosen
Indicates that a museum is located at the site of a former headquarters of an entity.
-
E.
formerSiteOf
Indicates that a location previously hosted or contained something (such as a structure, organization, or event) that is no longer present there.
- 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_69f2247db1108190835c0727c97637c3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a00acf86e4081909aad9356650e0f79 |
completed | May 10, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_6a00ac813fd08190a0a7782609e74e70 |
completed | May 10, 2026, 4:04 p.m. |
Created at: April 29, 2026, 7:29 p.m.