Triple
T29271605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trabi durch die Mauer |
E742131
|
entity |
| Predicate | onStructure |
P5886
|
FINISHED |
| Object | former Berlin Wall |
—
|
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: former Berlin Wall | Statement: [Trabi durch die Mauer, onStructure, former Berlin Wall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onStructure Context triple: [Trabi durch die Mauer, onStructure, former Berlin Wall]
-
A.
indicatesStructure
Indicates that one entity specifies, defines, or reveals the structural organization or arrangement of another entity.
-
B.
managesStructure
Indicates that one entity is responsible for overseeing, organizing, or administering the operation and maintenance of a particular structure.
-
C.
addedStructure
Indicates that one entity has introduced or incorporated an additional structural element into another entity or system.
-
D.
definesStructure
Indicates that one entity specifies or determines the organizational form, composition, or arrangement of another entity.
-
E.
viaStructure
chosen
Indicates that one entity is connected to or accessed through a particular structural element or medium.
- 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_69f0912124d48190a046642b69407f4c |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f664e41e5c81909063c310f222946b |
completed | May 2, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 12:48 p.m.