Triple
T14234371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | For the Union Dead |
E352834
|
entity |
| Predicate | timePeriodReflected |
P113319
|
FINISHED |
| Object | mid-20th-century America |
—
|
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: mid-20th-century America | Statement: [For the Union Dead, timePeriodReflected, mid-20th-century America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodReflected Context triple: [For the Union Dead, timePeriodReflected, mid-20th-century America]
-
A.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
B.
timePeriodOfRefinement
Indicates the specific time span during which a refinement or improvement of something takes place.
-
C.
timePeriodProposed
Indicates that a specific time period has been suggested or put forward for consideration or adoption.
-
D.
timePeriodOrigin
Indicates that one entity is the time period in which the other entity originated or first came into existence.
-
E.
timePerspective
Indicates how an entity conceptually relates to or orients itself toward time, such as focusing on past, present, or future.
- F. None of above. chosen
Provenance (4 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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de62411c888190a154acd56fe3fcaf |
completed | April 14, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69de05bf069c8190b69f00f00f5eb126 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239a02e881909b0e2679487e4ab2 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 10, 2026, 1:07 a.m.