Triple
T4000801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Combat Action Badge |
E89408
|
entity |
| Predicate | retroactiveDate |
P36523
|
FINISHED |
| Object | 18 September 2001 |
—
|
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: 18 September 2001 | Statement: [Combat Action Badge, retroactiveDate, 18 September 2001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retroactiveDate Context triple: [Combat Action Badge, retroactiveDate, 18 September 2001]
-
A.
isRetroactive
chosen
Indicates that an action, rule, or effect applies to a time period before its creation, enactment, or implementation.
-
B.
retrocessionDate
Indicates the date on which rights, obligations, or control previously transferred are formally returned or reassigned back to the original party or another designated party.
-
C.
doesNotApplyRetroactivelyTo
Indicates that a rule, law, or condition does not affect events, actions, or situations that occurred before it came into effect.
-
D.
reenvisionedDate
Indicates the date on which something was newly reimagined, redesigned, or conceptually revised.
-
E.
holdingDate
Indicates the date on which a holding, possession, or ownership of something is recorded or takes effect.
- 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_69aed9585e788190bec2d39deba3750f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefa8579288190940487ad07e38de0 |
completed | March 9, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69aef8f89f2881909b0965419d15d46c |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:34 p.m.