Triple
T23705393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Jewel Movement |
E585704
|
entity |
| Predicate | governedToYear |
P153649
|
FINISHED |
| Object | 1983 |
—
|
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: 1983 | Statement: [New Jewel Movement, governedToYear, 1983]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governedToYear Context triple: [New Jewel Movement, governedToYear, 1983]
-
A.
governedDuringPeriod
Indicates that a governing entity exercised authority or control over another entity throughout a specified time period.
-
B.
governedFor
Indicates that one entity exercised governing authority or administrative control on behalf of, or in the interest of, another entity.
-
C.
governedFrom
Indicates that an entity exercises governing authority or administrative control over another entity from a specific location or seat of power.
-
D.
governedByInPast
Indicates that an entity was under the rule, control, or authority of another entity during a previous time period.
-
E.
governedAs
Indicates that one entity exercises authoritative control, direction, or rule over another according to some system of governance or leadership.
- 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_69e24904bd508190abfcb74855de2918 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b686ef50819090a85e3ed40cfba1 |
completed | April 29, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f15b453da88190889a8d9b21727958 |
completed | April 29, 2026, 1:13 a.m. |
Created at: April 17, 2026, 6:53 p.m.