Triple
T36421985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resident Magistrates’ Courts |
E897181
|
entity |
| Predicate | wereRenamedAs |
P185477
|
FINISHED |
| Object | Parish Courts of Jamaica |
—
|
NE NERFINISHED |
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: Parish Courts of Jamaica | Statement: [Resident Magistrates’ Courts, wereRenamedAs, Parish Courts of Jamaica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wereRenamedAs Context triple: [Resident Magistrates’ Courts, wereRenamedAs, Parish Courts of Jamaica]
-
A.
wasRenamedIn
Indicates that an entity changed its name to a different one at or during a specific time or event.
-
B.
wasRenamedBackTo
Indicates that an entity, after having its name changed, was later restored to its previous or original name.
-
C.
oftenRenamedAs
Indicates that an entity is frequently given a different name or title, reflecting common renaming or rebranding over time or across contexts.
-
D.
renamedDueTo
Indicates that one entity was renamed as a consequence of another specified cause, event, or condition.
-
E.
willBeRenamedAs
Indicates that an entity is planned or expected to receive a new name specified by another entity.
- 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_69f76e559b10819099d6655a6e14587c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69f7be9b9ab481908328e0e8d8ac73d4 |
completed | May 3, 2026, 9:31 p.m. |
Created at: May 3, 2026, 4:10 p.m.