Triple
T26864459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | coat of arms of Stuttgart |
E676424
|
entity |
| Predicate | chargeAttitude |
P161972
|
FINISHED |
| Object | rampant |
—
|
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: rampant | Statement: [coat of arms of Stuttgart, chargeAttitude, rampant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chargeAttitude Context triple: [coat of arms of Stuttgart, chargeAttitude, rampant]
-
A.
primaryChargeAttitude
Indicates the stance or evaluative attitude an agent holds toward a primary charge or accusation in a given context.
-
B.
charge
Indicates that one entity formally accuses another of an offense or imposes a financial cost or obligation on them.
-
C.
chargeParity
Indicates that two related entities share the same electric charge sign (parity), such as both being positively or both negatively charged.
-
D.
chargeOnChief
Indicates that a formal accusation or legal charge is filed against a chief or primary authority figure.
-
E.
chargeType
Indicates the category or nature of a charge applied in a transaction or interaction between entities (e.g., fee type, billing classification, or legal charge type).
- 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_69eee9ba94bc8190b44c5d4397d04ecd |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f62081136c81909de8090b1d6c1ac5 |
completed | May 2, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61fd5442081908ca677a9c81dcb3f |
completed | May 2, 2026, 4:01 p.m. |
Created at: April 27, 2026, 5:27 a.m.