Triple
T18632929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Bank of Denmark building |
E455466
|
entity |
| Predicate | minimalistForm |
P132474
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [National Bank of Denmark building, minimalistForm, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minimalistForm Context triple: [National Bank of Denmark building, minimalistForm, yes]
-
A.
nativeForm
Indicates that one entity is the original or native linguistic form of another, such as a word’s form in its source language.
-
B.
masslessForm
Indicates that an entity exists or is represented in a form that has no mass.
-
C.
visualForm
Indicates the visual appearance, shape, or structural pattern that characterizes how something looks.
-
D.
typicalForm
Indicates that one entity represents the standard, characteristic, or most common form or shape in which another entity typically appears or is realized.
-
E.
exportForm
Indicates that one entity sends or transfers something (such as goods, data, or a document) out from its origin to another place, system, or jurisdiction in a specified format.
- 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_69d8d38cc7948190a55ea64e5638994e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54fc5c7ec8190ab0c64f009583f96 |
completed | April 19, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69e478d4a7948190a4bb9223bb5dddfc |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e485f5d1588190b44f31cbc54c0a9d |
completed | April 19, 2026, 7:36 a.m. |
Created at: April 10, 2026, 11:46 a.m.