Triple
T3478489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brandenburg Gate (Potsdam) |
E73432
|
entity |
| Predicate | westFrontStyle |
P45253
|
FINISHED |
| Object | Roman triumphal arch inspired design |
—
|
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: Roman triumphal arch inspired design | Statement: [Brandenburg Gate (Potsdam), westFrontStyle, Roman triumphal arch inspired design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: westFrontStyle Context triple: [Brandenburg Gate (Potsdam), westFrontStyle, Roman triumphal arch inspired design]
-
A.
frontType
Indicates the type or category of a front (e.g., boundary or leading side) that one entity presents or forms relative to another.
-
B.
frontSightType
Indicates the specific kind or design of the front sight used on an object, typically a firearm or similar aiming device.
-
C.
partOfFront
Indicates that one entity constitutes a component or section located at the front portion of another entity.
-
D.
frontDesign
chosen
Indicates that one entity serves as the primary or visible front-facing design or appearance of another entity.
-
E.
westernGate
Indicates that one entity serves as the western gate or western entrance relative to another entity.
- 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_69ad85b3c9b08190857cae74c7f36da9 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb5ca73c81908256e3339a3a6f9f |
completed | March 8, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69adae0935ac8190bfa8a8bd3dcd3301 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:17 p.m.