Triple
T3834385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blackhorse insignia |
E91092
|
entity |
| Predicate | wearerType |
P52283
|
FINISHED |
| Object | officers of the 11th Armored Cavalry Regiment |
—
|
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: officers of the 11th Armored Cavalry Regiment | Statement: [Blackhorse insignia, wearerType, officers of the 11th Armored Cavalry Regiment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wearerType Context triple: [Blackhorse insignia, wearerType, officers of the 11th Armored Cavalry Regiment]
-
A.
wearerStatus
Indicates the condition or role of an entity in its capacity as a wearer of something (e.g., clothing, equipment, or an accessory).
-
B.
wearerTitle
Indicates that a specified title or designation is held by the wearer of an item or garment.
-
C.
wearerDevice
Indicates that a device is worn or carried by a particular entity (the wearer).
-
D.
wears
Indicates that one entity is dressed in, or has on its body, a particular item such as clothing or accessories.
-
E.
wearClassification
Indicates a classification relationship specifying the type or category of wear associated with an entity or interaction.
- F. None of above. chosen
Provenance (4 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_69aed960b538819096561c8ed448dec9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeeb8a27688190866bc41441e2260c |
completed | March 9, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69aee74c2e04819094b94b3c0bac1806 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aeeb828fb08190901d51edbe8bd304 |
completed | March 9, 2026, 3:47 p.m. |
Created at: March 9, 2026, 3:18 p.m.