Triple
T1658899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canadian Forces Reorganization Act |
E35860
|
entity |
| Predicate | decadeEnacted |
P10966
|
FINISHED |
| Object | 1960s |
—
|
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: 1960s | Statement: [Canadian Forces Reorganization Act, decadeEnacted, 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decadeEnacted Context triple: [Canadian Forces Reorganization Act, decadeEnacted, 1960s]
-
A.
developmentStartDecade
Indicates the decade during which the development or creation of an entity was initiated.
-
B.
decade
Indicates that the relationship or event is associated with, occurs within, or is characteristic of a specific ten-year time period.
-
C.
endedInDecade
Indicates that an event, process, or state concluded during a specified decade.
-
D.
emergedInDecade
Indicates that something first appeared, originated, or came into prominence during a specified decade.
-
E.
cameIntoEffectInDecade
chosen
Indicates that something (such as a law, policy, or agreement) officially began to be in force during a specified decade.
- 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_69a88606aa808190aa0b421b4271f220 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf3359ce48190803b322db8ad6027 |
completed | March 6, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69a907cff53c8190b424f088478d3e2c |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:29 p.m.