Triple
T8912142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 63rd (West Suffolk) Regiment of Foot |
E212208
|
entity |
| Predicate | facingsColour |
P44517
|
FINISHED |
| Object | dark green facings |
—
|
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: dark green facings | Statement: [63rd (West Suffolk) Regiment of Foot, facingsColour, dark green facings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: facingsColour Context triple: [63rd (West Suffolk) Regiment of Foot, facingsColour, dark green facings]
-
A.
uniformFacingsColour
chosen
Indicates that the facings (such as cuffs, collars, or lapels) on a uniform share the same color.
-
B.
parchmentColor
Indicates that one entity has the color characteristic of parchment in relation to another entity.
-
C.
designedToFace
Indicates that one entity has been intentionally oriented or configured so that its front, surface, or primary direction points toward another entity or reference direction.
-
D.
frontDesignSameAsBack
Indicates that the design on the front side of an object is identical to the design on its back side.
-
E.
coverArtFeaturesColor
Indicates that the cover art includes or prominently displays a specific color as part of its visual design.
- 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_69ca8393b1808190bd4336787ffa2c40 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6525d1408190a76522d7c4ac37da |
completed | April 1, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69cc5ecf55248190a29f00fbf99f13c4 |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:56 p.m.