Triple
T12631328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | flag of Mecklenburg-Vorpommern |
E301647
|
entity |
| Predicate | hasStripeWidth |
P106117
|
FINISHED |
| Object | narrow white stripe |
—
|
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: narrow white stripe | Statement: [flag of Mecklenburg-Vorpommern, hasStripeWidth, narrow white stripe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStripeWidth Context triple: [flag of Mecklenburg-Vorpommern, hasStripeWidth, narrow white stripe]
-
A.
hasStripeColor
Indicates that an entity possesses stripes of a specified color.
-
B.
topStripeWidth
Indicates the width measurement of the topmost stripe in a striped object or pattern.
-
C.
hasStripeOrientation
Indicates the directional arrangement or alignment of stripes present on an entity.
-
D.
centralStripeWidth
Indicates the width measurement of the central stripe in a striped pattern or design.
-
E.
yellowStripeWidthRatio
Indicates the proportional width of a yellow stripe relative to a reference dimension (such as the total width or height of the object it appears on).
- 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ae493481908f82e0d05dce20bd |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960b47130819097e1162ed4fc993a |
completed | April 10, 2026, 8:42 p.m. |
| PDg | Predicate description generation | batch_69d961acadb8819098de743bc951fedb |
completed | April 10, 2026, 8:46 p.m. |
Created at: April 9, 2026, 5:15 p.m.