Triple
T9962017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flag of Belgium |
E195590
|
entity |
| Predicate | writingDirectionOfStripes |
P77290
|
FINISHED |
| Object | hoist to fly |
—
|
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: hoist to fly | Statement: [Flag of Belgium, writingDirectionOfStripes, hoist to fly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writingDirectionOfStripes Context triple: [Flag of Belgium, writingDirectionOfStripes, hoist to fly]
-
A.
orderOfStripes
chosen
Indicates the sequential arrangement or pattern in which stripes appear relative to one another.
-
B.
orangeStripeRepresents
Indicates that an orange stripe symbolically stands for, denotes, or conveys the meaning of a particular concept, status, or entity.
-
C.
flankedByStripes
Indicates that an entity is positioned between or bordered on both sides by stripe-like elements.
-
D.
yellowStripeRepresents
Indicates that a yellow stripe symbolically stands for or denotes a particular meaning, status, or attribute in a given context.
-
E.
hasWritingDirection
Indicates the direction in which writing or text is read or written for a given script, language, or text system.
- 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_69ca82ebd1288190912f9e4482d1fa35 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb6d37f0c8190946b958c399f3250 |
completed | April 2, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9ae19c819099fb3635e57c79be |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:47 p.m.