Triple
T28572305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of Senegal |
E723145
|
entity |
| Predicate | chargeOnDexter |
P164883
|
FINISHED |
| Object | gold lion passant |
—
|
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: gold lion passant | Statement: [Coat of arms of Senegal, chargeOnDexter, gold lion passant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chargeOnDexter Context triple: [Coat of arms of Senegal, chargeOnDexter, gold lion passant]
-
A.
chargeOnChief
Indicates that a formal accusation or legal charge is filed against a chief or primary authority figure.
-
B.
chargesVia
Indicates that one entity charges or powers another entity using a specified medium, method, or interface.
-
C.
chargedOn
Indicates that a fee, cost, or financial amount is applied to an account, entity, or transaction at a specific time or in connection with a particular event.
-
D.
chargesWere
Indicates that specific accusations or legal charges existed or were formally brought against an entity at some point in time.
-
E.
charge
Indicates that one entity formally accuses another of an offense or imposes a financial cost or obligation on them.
- 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_69f01d7e97708190ae9e77ee66a68abd |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f652a3a8208190a4fdd66f34138bd2 |
completed | May 2, 2026, 7:38 p.m. |
Created at: April 28, 2026, 4:10 a.m.