Triple
T23118639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of Serbia |
E576826
|
entity |
| Predicate | mainChargeColor |
P150975
|
FINISHED |
| Object | white |
—
|
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: white | Statement: [Coat of arms of Serbia, mainChargeColor, white]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainChargeColor Context triple: [Coat of arms of Serbia, mainChargeColor, white]
-
A.
hasChargeColor
Indicates that one entity is associated with a particular color used to represent its electric charge or charge state.
-
B.
colorCharge
Indicates a relationship where an entity possesses a specific quantum color charge (such as red, green, or blue) in the context of strong nuclear interactions.
-
C.
chargeColour
Indicates that one entity assigns or possesses a specific color associated with an electrical or physical charge of another entity.
-
D.
mainCharge
Indicates that one charge in a set of legal accusations is designated as the primary or most significant offense.
-
E.
isColorCharged
Indicates that an entity possesses color charge, meaning it carries the type of charge associated with the strong nuclear interaction in quantum chromodynamics.
- 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_69e245f6c2e881909a228fdcfeb7c7d3 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e4dd7d8819087cc50b2dc94798e |
completed | April 29, 2026, 4:51 a.m. |
| PD | Predicate disambiguation | batch_69ef89f020588190b43393e048e7eda3 |
completed | April 27, 2026, 4:08 p.m. |
| PDg | Predicate description generation | batch_69ef9b7494f4819088ae59ea3d0ae8ab |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 3:59 p.m.