Triple
T28187344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bordered Yellow Banner |
E716213
|
entity |
| Predicate | statusWithinEightBanners |
P82706
|
FINISHED |
| Object | upper three banners |
—
|
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: upper three banners | Statement: [Bordered Yellow Banner, statusWithinEightBanners, upper three banners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusWithinEightBanners Context triple: [Bordered Yellow Banner, statusWithinEightBanners, upper three banners]
-
A.
rankWithinEightBanners
Indicates that an entity holds a specific rank or position within the organizational structure of the Eight Banners system.
-
B.
statusAfter1808
Indicates the condition or classification of something as it existed or was defined after the year 1808.
-
C.
usedBanner
Indicates that one entity employed or displayed another entity as a banner in some context or setting.
-
D.
presentedUnderBanner
chosen
Indicates that something is displayed or showcased beneath or associated with a specific banner or heading.
-
E.
statusAfter680
Indicates that an entity’s status or condition holds or applies after the point identified as 680 (e.g., a time, event, or version marker).
- 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_69efd6b612f48190a72012b520afbd10 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: April 27, 2026, 10:23 p.m.