Triple
T22663502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian Air Force roundel |
E559721
|
entity |
| Predicate | outermostBandRepresents |
P139251
|
FINISHED |
| Object | saffron of Indian flag |
—
|
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: saffron of Indian flag | Statement: [Indian Air Force roundel, outermostBandRepresents, saffron of Indian flag]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outermostBandRepresents Context triple: [Indian Air Force roundel, outermostBandRepresents, saffron of Indian flag]
-
A.
outermostZone
Indicates that one entity is the outermost or furthest boundary zone enclosing or surrounding another entity or area.
-
B.
outerBoundary
chosen
Indicates that one entity serves as the enclosing outer limit or perimeter that bounds another entity or region.
-
C.
topLevelRepresents
Indicates that one entity serves as the primary or overarching representation of another entity or concept at the highest level of abstraction or organization.
-
D.
observesBand
Indicates that one entity watches, studies, or monitors a musical band.
-
E.
visibleInBand
Indicates that something can be observed or detected within a specified spectral band or range of wavelengths.
- 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_69e2454a158c819093b8e35f5045efb6 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f176617ed8819095a58a2c9f1e3918 |
completed | April 29, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69ee62a6245881909506ff502da14137 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:08 p.m.