Triple
T34997533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | York and Lancaster Regiment |
E1009579
|
entity |
| Predicate | regimentalColourFeature |
P129524
|
FINISHED |
| Object | white rose of York |
—
|
NE NERFINISHED |
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: white rose of York | Statement: [York and Lancaster Regiment, regimentalColourFeature, white rose of York]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regimentalColourFeature Context triple: [York and Lancaster Regiment, regimentalColourFeature, white rose of York]
-
A.
regimentalColourSymbol
chosen
Indicates that something serves as the symbolic emblem or design used on a regiment’s official flag or standard.
-
B.
regimentalBadgeFeature
Indicates that one entity serves as a design element or component featured on a regiment’s badge.
-
C.
corpsColour
Indicates the specific color associated with a military corps or unit.
-
D.
heraldicColor
Indicates that one entity specifies or bears a particular heraldic color in a coat of arms or related heraldic context.
-
E.
isRegimentalTartanOf
Indicates that one tartan pattern is officially designated as the regimental tartan of a particular military regiment.
- 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_69f76dca50dc8190b71f39defe186be8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.