Triple
T30980533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flag of Rwanda |
E789358
|
entity |
| Predicate | bottomBandWidth |
P104572
|
FINISHED |
| Object | one quarter of flag height |
—
|
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: one quarter of flag height | Statement: [Flag of Rwanda, bottomBandWidth, one quarter of flag height]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bottomBandWidth Context triple: [Flag of Rwanda, bottomBandWidth, one quarter of flag height]
-
A.
lowerBandWidth
Indicates that one entity has a smaller or more limited bandwidth capacity than another.
-
B.
bottomStripeWidth
chosen
Indicates the width measurement of the stripe located at the bottom of an object or surface.
-
C.
bottomStripePosition
Indicates the vertical placement of the bottom stripe relative to a reference frame or object.
-
D.
upperBandWidth
Indicates the maximum bandwidth limit or upper threshold of data transfer capacity allowed or supported in a given context.
-
E.
whiteBandWidthRelation
Indicates a relationship where one entity’s white band (or white-bandwidth) measurement is compared to or constrained by another entity’s corresponding white band value.
- 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_69f224c4831c8190be53924ec25a150a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:55 p.m.