Triple
T1411880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flag of the African Union |
E31822
|
entity |
| Predicate | rayShape |
P26638
|
FINISHED |
| Object | stylized rays around the map of Africa |
—
|
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: stylized rays around the map of Africa | Statement: [Flag of the African Union, rayShape, stylized rays around the map of Africa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rayShape Context triple: [Flag of the African Union, rayShape, stylized rays around the map of Africa]
-
A.
baseShape
Indicates that one entity serves as the fundamental or underlying shape or form upon which another entity is defined, derived, or constructed.
-
B.
coreShape
Indicates that one entity serves as the primary or central shape or geometric form of another entity.
-
C.
shape
Indicates that one entity has a particular geometric or physical form characterized by the other entity.
-
D.
ringPlane
Indicates that one entity lies within or corresponds to the geometric plane defined by a ring structure associated with another entity.
-
E.
shaped
Indicates that one entity has given form, contour, or structure to another entity or outcome.
- 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_69a49919a994819086528951bc224775 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3e3383c81909acb9c6c1c3b817a |
completed | March 1, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69a4bf048b648190ab77d9b45cb4855f |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4bf8158ac8190b8360ecccc2980bc |
completed | March 1, 2026, 10:36 p.m. |
Created at: March 1, 2026, 7:59 p.m.