Triple
T25736864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of Venezuela |
E645398
|
entity |
| Predicate | chargeOnBlueField |
P159803
|
FINISHED |
| Object | white horse |
—
|
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 horse | Statement: [Coat of arms of Venezuela, chargeOnBlueField, white horse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chargeOnBlueField Context triple: [Coat of arms of Venezuela, chargeOnBlueField, white horse]
-
A.
chargeOnYellowField
Indicates that an entity performs or initiates a charge (rapid advance or attack) while on a yellow-colored field or background.
-
B.
chargeOnRedField
Indicates that an entity bears or displays a charge (such as a symbol or emblem) positioned on a red-colored field or background.
-
C.
chargeOnChief
Indicates that a formal accusation or legal charge is filed against a chief or primary authority figure.
-
D.
chargeColour
Indicates that one entity assigns or possesses a specific color associated with an electrical or physical charge of another entity.
-
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_69e77e85254081908d79ee4e8715f283 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fd1655c081908933b34ba0387479 |
completed | May 2, 2026, 1:33 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 21, 2026, 11:27 p.m.