Triple
T18120609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bevin Boys Veterans Badge |
E433719
|
entity |
| Predicate | timePeriodRecognised |
P56928
|
FINISHED |
| Object | 1939–1945 |
—
|
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: 1939–1945 | Statement: [Bevin Boys Veterans Badge, timePeriodRecognised, 1939–1945]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodRecognised Context triple: [Bevin Boys Veterans Badge, timePeriodRecognised, 1939–1945]
-
A.
timePeriodRecognized
chosen
Indicates that a specific span of time has been formally identified or acknowledged as significant or valid within a given context.
-
B.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
C.
timePeriodFormulated
Indicates the time period during which something (such as a concept, theory, or plan) was formulated or developed.
-
D.
timePeriodImplied
Indicates that a time period is inferred or implied by context rather than being explicitly specified.
-
E.
timePeriodCategory
Indicates the classification of a time period into a specific category or type (e.g., era, phase, or temporal grouping).
- 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_69d8b909e8cc81908df4cc2b8ea6d11f |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddd9b21c81908d23b8d9840410df |
completed | April 19, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_69e43313ca788190baa224269e71de49 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:28 a.m.