Triple
T8535888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Confederate infantry |
E202075
|
entity |
| Predicate | woreHeadgear |
P271
|
FINISHED |
| Object | slouch hat |
—
|
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: slouch hat | Statement: [Confederate infantry, woreHeadgear, slouch hat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: woreHeadgear Context triple: [Confederate infantry, woreHeadgear, slouch hat]
-
A.
associatedWithHeadgear
Indicates a relationship where an entity is connected or related to a particular item of headgear, such as by wearing, using, or being characterized by it.
-
B.
authorizedHeadgear
Indicates that a particular item of headgear is officially permitted or approved for use in a given context or by a specific authority.
-
C.
helmetColor
Indicates the specific color attribute assigned to a helmet in the relationship.
-
D.
wears
chosen
Indicates that one entity is dressed in, or has on its body, a particular item such as clothing or accessories.
-
E.
wornAround
Indicates that one entity is physically worn encircling or surrounding another entity (e.g., around a body part or object).
- 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_69ca832355b08190b8b6a4ab4a4a3554 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe6a295c88190a432a060ee73f04e |
completed | March 31, 2026, 3:22 p.m. |
| PD | Predicate disambiguation | batch_69cbd111bf988190be98c92a607c6456 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:17 p.m.