Triple
T27174353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berlin Wall Memorial at Bernauer Straße |
E683001
|
entity |
| Predicate | memorialLength |
P167119
|
FINISHED |
| Object | approximately 1.4 kilometers |
—
|
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: approximately 1.4 kilometers | Statement: [Berlin Wall Memorial at Bernauer Straße, memorialLength, approximately 1.4 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memorialLength Context triple: [Berlin Wall Memorial at Bernauer Straße, memorialLength, approximately 1.4 kilometers]
-
A.
memorialType
Indicates the specific kind or category of memorial associated with an entity (e.g., plaque, statue, monument).
-
B.
numberCommemoratedOnMemorial
Indicates the quantity of individuals or entities that are honored or remembered on a particular memorial.
-
C.
hasMemorial
Indicates that a memorial exists in honor of, or dedicated to, a particular entity.
-
D.
memorialScope
Indicates the extent or boundaries of what is commemorated or covered by a memorial.
-
E.
memorialOpenedInYear
Indicates that a memorial was officially opened or inaugurated in a specified calendar year.
- 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_69eefad086808190ab89816c0c300476 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6653ccf648190b65fb1141928e47e |
completed | May 2, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f663ff176c8190aaadb475f75daee4 |
completed | May 2, 2026, 8:52 p.m. |
Created at: April 27, 2026, 9:25 a.m.