Triple
T36248950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of Bremen |
E891741
|
entity |
| Predicate | hasKeyBitShape |
P96593
|
FINISHED |
| Object | stylized cross-shaped bit |
—
|
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: stylized cross-shaped bit | Statement: [Coat of arms of Bremen, hasKeyBitShape, stylized cross-shaped bit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyBitShape Context triple: [Coat of arms of Bremen, hasKeyBitShape, stylized cross-shaped bit]
-
A.
hasBit
Indicates that one entity possesses, contains, or includes a specific bit or binary position/value of another entity.
-
B.
hasKeyStructure
chosen
Indicates that one entity possesses or defines the primary structural framework or core structural pattern of another entity.
-
C.
hasKeyFigure
Indicates that an entity includes, involves, or is characterized by an important or central person relevant to it.
-
D.
hasKeyType
Indicates that an entity possesses or is associated with a specific category or type of key.
-
E.
hasKeySupporter
Indicates that an entity has a primary or crucial supporter who significantly backs or advocates for it.
- 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_69f76e4599108190811532e707d6bc2c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.