Triple
T4508040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 15th Light Dragoons |
E101980
|
entity |
| Predicate | uniformFacings |
P44517
|
FINISHED |
| Object | distinctive regimental 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: distinctive regimental facings | Statement: [15th Light Dragoons, uniformFacings, distinctive regimental facings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: uniformFacings Context triple: [15th Light Dragoons, uniformFacings, distinctive regimental facings]
-
A.
uniformFacingsColour
chosen
Indicates that the facings (such as cuffs, collars, or lapels) on a uniform share the same color.
-
B.
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.
-
C.
facesBuilding
Indicates that one building is oriented toward and directly faces another building.
-
D.
façadeOrientation
Indicates the directional orientation that a building’s façade faces relative to a reference (e.g., cardinal directions or a main street).
-
E.
facedBy
Indicates that one entity is oriented toward and directly opposite another entity, such that it is facing it.
- 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_69bd43d6251c81909deecce3e6e9d69c |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd570f9b1c8190b52ace855dbf6641 |
completed | March 20, 2026, 2:17 p.m. |
| PD | Predicate disambiguation | batch_69bd5218afb4819087c99e0a1f22e137 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:01 p.m.