Triple
T35640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army Green Service Uniform |
E705
|
entity |
| Predicate | announced |
P429
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Army Green Service Uniform, announced, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: announced Context triple: [Army Green Service Uniform, announced, 2018]
-
A.
announcedAt
Indicates that an announcement or declaration was made at a specific time or event.
-
B.
announcedPledge
Indicates that an entity has publicly declared a commitment or promise, typically regarding future actions or contributions.
-
C.
announcementDate
chosen
Indicates the date on which an announcement is formally made or becomes publicly known.
-
D.
announcedInCity
Indicates that an announcement or declaration was formally made within a particular city.
-
E.
introduced
Indicates that one entity caused another entity to become known, presented, or brought into use for the first time to a person, group, or 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_69a2479dec388190967ba648663442c9 |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a24989c3308190af59dfae37cfc32f |
completed | Feb. 28, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69a24873e97c8190b9e4279e43b6de14 |
completed | Feb. 28, 2026, 1:44 a.m. |
Created at: Feb. 28, 2026, 1:44 a.m.