Triple
T33936411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akita Prefecture flag |
E870043
|
entity |
| Predicate | writingDirectionOfEmblem |
P172689
|
FINISHED |
| Object | left-to-right stylization |
—
|
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: left-to-right stylization | Statement: [Akita Prefecture flag, writingDirectionOfEmblem, left-to-right stylization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writingDirectionOfEmblem Context triple: [Akita Prefecture flag, writingDirectionOfEmblem, left-to-right stylization]
-
A.
hasWritingDirection
Indicates the direction in which writing or text is read or written for a given script, language, or text system.
-
B.
writingDirectionStatus
chosen
Indicates the current state or condition of an entity’s writing direction (e.g., left-to-right, right-to-left, or unspecified).
-
C.
emblemLanguage
Indicates that an emblem (such as a symbol or logo) is associated with or presented in a particular language.
-
D.
emblemText
Indicates that a piece of text serves as the inscription or wording displayed on an emblem.
-
E.
orientationInFlag
Indicates the spatial orientation or alignment of an entity as it appears within a flag.
- F. None of above.
Provenance (3 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_69f3499a59788190bff762a891471b31 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7064e906881909c3186c646145d34 |
completed | May 3, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69f70100ec1c8190a6b97f50e88891f2 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:49 a.m.