Triple
T2065903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CNSAS archives |
E45898
|
entity |
| Predicate | focusPeriodStart |
P35135
|
FINISHED |
| Object | late 1940s |
—
|
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: late 1940s | Statement: [CNSAS archives, focusPeriodStart, late 1940s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusPeriodStart Context triple: [CNSAS archives, focusPeriodStart, late 1940s]
-
A.
focusPeriod
Indicates the specific time span during which attention, activity, or analysis is concentrated on something.
-
B.
coversPeriodStart
Indicates that the time span or coverage of one entity begins at, or includes, the specified starting point in time of another entity or period.
-
C.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
D.
banPeriodStart
Indicates the date or time at which a ban or prohibition begins to take effect.
-
E.
typicalStartPeriod
Indicates the usual or standard time period during which something begins or is initiated.
- 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_69a8891b38288190abd572ccad9b6928 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9f0cb888190a97884f5a722d91f |
completed | March 7, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69abb7aee9b48190999620176e3a6ee2 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb87b9fc08190a748c278ef2d7dc7 |
completed | March 7, 2026, 5:32 a.m. |
Created at: March 4, 2026, 7:40 p.m.