Triple
T14522117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emblem of Somalia |
E340677
|
entity |
| Predicate | hasShieldCharge |
P114578
|
FINISHED |
| Object | golden 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: golden five-pointed star | Statement: [Emblem of Somalia, hasShieldCharge, golden five-pointed star]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShieldCharge Context triple: [Emblem of Somalia, hasShieldCharge, golden five-pointed star]
-
A.
hasShieldBearer
Indicates that one entity serves as the shield-bearing protector or defensive attendant for another entity.
-
B.
chargesOnShield
Indicates that an entity moves aggressively forward to attack while using a shield as protection or impact.
-
C.
shieldPresent
Indicates that a protective shield is currently active or available in the given context.
-
D.
canHoldAdditionalChargeOf
Indicates that one entity has the capacity to store or accommodate an additional specified amount of electric charge beyond its current level.
-
E.
shieldsStatusOnLaunch
Indicates that the status or condition of shields is set or evaluated at the moment of launch.
- 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_69d822dac79c8190a84a073f3cbaced5 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69de9a72cff08190878b4bed9b0b5eb5 |
completed | April 14, 2026, 7:50 p.m. |
| PD | Predicate disambiguation | batch_69de5c518fc08190a6ce4d8be05c4c5d |
completed | April 14, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69de5fb5ac548190932f238e37271741 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:22 a.m.