Triple
T471608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army Combat Uniform |
E8569
|
entity |
| Predicate | regulatesInsigniaPlacement |
P3020
|
FINISHED |
| Object | name tape |
—
|
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: name tape | Statement: [Army Combat Uniform, regulatesInsigniaPlacement, name tape]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatesInsigniaPlacement Context triple: [Army Combat Uniform, regulatesInsigniaPlacement, name tape]
-
A.
hasSignage
Indicates that appropriate signs or visual markers are present to convey information, directions, warnings, or identification related to the associated entity.
-
B.
signageStandard
Indicates that something conforms to, follows, or specifies a particular standard or convention for signage.
-
C.
hasCurrencySignPlacement
Indicates where the currency sign is positioned relative to the numeric amount in a monetary value.
-
D.
regulatesFacility
Indicates that one entity has authority to control, oversee, or set rules governing the operation or behavior of a facility.
-
E.
regulatesUse
chosen
Indicates that one entity controls, governs, or sets rules for how another entity may be used.
- 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_69a2e7f3aeb48190a19453e3a043f486 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eff0ca408190958405aec2ec6f53 |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2edecefb081908331ef8b9edf6636 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.