Triple
T28572306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of Senegal |
E723145
|
entity |
| Predicate | chargeOnSinister |
P165461
|
FINISHED |
| Object | green baobab tree |
—
|
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: green baobab tree | Statement: [Coat of arms of Senegal, chargeOnSinister, green baobab tree]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chargeOnSinister Context triple: [Coat of arms of Senegal, chargeOnSinister, green baobab tree]
-
A.
chargeOnChief
Indicates that a formal accusation or legal charge is filed against a chief or primary authority figure.
-
B.
chargeAgainstPerpetrator
Indicates that a formal legal accusation or charge has been brought against a specific perpetrator for an alleged offense.
-
C.
chargesVia
Indicates that one entity charges or powers another entity using a specified medium, method, or interface.
-
D.
charge
Indicates that one entity formally accuses another of an offense or imposes a financial cost or obligation on them.
-
E.
chargesOnShield
Indicates that an entity moves aggressively forward to attack while using a shield as protection or impact.
- 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_69f659355a208190be2609ffc7a9c427 |
completed | May 2, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f65875030881909007c502b7dcc998 |
completed | May 2, 2026, 8:03 p.m. |
Created at: April 28, 2026, 4:10 a.m.