Triple
T36421785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Traffic Court of Jamaica |
E897176
|
entity |
| Predicate | hearsCaseAgainst |
P18526
|
FINISHED |
| Object | drivers |
—
|
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: drivers | Statement: [Traffic Court of Jamaica, hearsCaseAgainst, drivers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hearsCaseAgainst Context triple: [Traffic Court of Jamaica, hearsCaseAgainst, drivers]
-
A.
hearsCasesAgainst
chosen
Indicates that one party (typically a judicial body or official) formally listens to and considers legal cases brought against another party.
-
B.
hearsAppealsAgainst
Indicates that one entity formally reviews and considers appeals challenging the decisions or actions of another entity.
-
C.
hearsCasesAs
Indicates that one judicial body or judge reviews and adjudicates cases originating from another court or jurisdiction.
-
D.
hearsAppealTo
Indicates that one entity formally reviews and considers an appeal submitted by another entity.
-
E.
hearsCasesWith
Indicates that one judicial body or judge conducts proceedings together with another judicial body or judge in hearing the same cases.
- 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_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. |
Created at: May 3, 2026, 4:10 p.m.