Triple
T159119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AGSU |
E3241
|
entity |
| Predicate | replacedUniform |
P3618
|
FINISHED |
| Object | Army Service Uniform (ASU) for most daily wear |
—
|
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: Army Service Uniform (ASU) for most daily wear | Statement: [AGSU, replacedUniform, Army Service Uniform (ASU) for most daily wear]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedUniform Context triple: [AGSU, replacedUniform, Army Service Uniform (ASU) for most daily wear]
-
A.
usesUniform
Indicates that one entity regularly wears or employs a standardized set of clothing or equipment designated as a uniform.
-
B.
replacedCurrency
Indicates that one currency has been superseded and no longer used because another currency has taken its place.
-
C.
replacedSystemUsedUntil
chosen
Indicates that one system was used up until it was replaced by another system.
-
D.
primaryUniformAssociation
Indicates that one entity is designated as the main or primary uniform associated with another entity.
-
E.
uniformDistinction
Indicates that a clear and consistent difference is maintained between two or more entities within a given context.
- 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a2583169a0819081b658882e5bc452 |
completed | Feb. 28, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69a25660c2a48190b4174d5e6da3cb9d |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.