Triple
T11635531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jamaica Independence Act 1962 |
E276507
|
entity |
| Predicate | inForceOnDate |
P17807
|
FINISHED |
| Object | 1962-08-06 |
—
|
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: 1962-08-06 | Statement: [Jamaica Independence Act 1962, inForceOnDate, 1962-08-06]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inForceOnDate Context triple: [Jamaica Independence Act 1962, inForceOnDate, 1962-08-06]
-
A.
inForceAtTime
Indicates that a rule, condition, or state is actively valid and applicable during a specified time or time interval.
-
B.
inForceInPeriod
Indicates that something (such as a rule, contract, or condition) is valid, applicable, or legally effective during a specified time period.
-
C.
inForceSince
chosen
Indicates that a rule, law, agreement, or condition has been officially in effect starting from a specified date or time.
-
D.
inForceIn
Indicates that a rule, law, agreement, or condition is currently valid and operative within a specified jurisdiction, context, or time frame.
-
E.
inForceAfter
Indicates that a condition, rule, or agreement becomes valid or operative only after a specified time, event, or state has occurred.
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a25c0b00819095898d2b2445ecfb |
completed | April 10, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dd94bdc819091fa2ed33eb31624 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.