Triple
T450651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of Chile |
E7118
|
entity |
| Predicate | centralCharge |
P13348
|
FINISHED |
| Object | white five-pointed star |
—
|
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 five-pointed star | Statement: [Coat of arms of Chile, centralCharge, white five-pointed star]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralCharge Context triple: [Coat of arms of Chile, centralCharge, white five-pointed star]
-
A.
charge
Indicates that one entity formally accuses another of an offense or imposes a financial cost or obligation on them.
-
B.
hasCharge
Indicates that an entity possesses a specific electrical or formal charge, such as positive, negative, or neutral.
-
C.
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.
-
D.
centerType
Indicates the classification or category of a center (e.g., type of facility, institution, or hub) associated with an entity.
-
E.
chargeOftenUsed
Indicates that an entity is frequently subjected to or associated with a particular charge (such as a legal, financial, or electrical charge).
- 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_69a2e7e4676c81909ea0dbdecac0687c |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ef691cc8819091729eaac52c9457 |
completed | Feb. 28, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69a2ede3187c8190a7ced078f0ec3476 |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eeba8a488190986cc7381332f783 |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.