Triple
T36310315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judiciary of the Turks and Caicos Islands |
E894048
|
entity |
| Predicate | finalAppealHeardIn |
P38362
|
FINISHED |
| Object | London |
—
|
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: London | Statement: [Judiciary of the Turks and Caicos Islands, finalAppealHeardIn, London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalAppealHeardIn Context triple: [Judiciary of the Turks and Caicos Islands, finalAppealHeardIn, London]
-
A.
hearsAppealsIn
Indicates that a judicial body has the authority to review and decide appeals within a specified jurisdiction or court.
-
B.
hearsAppealTo
Indicates that one entity formally reviews and considers an appeal submitted by another entity.
-
C.
hearsAppealsAgainst
Indicates that one entity formally reviews and considers appeals challenging the decisions or actions of another entity.
-
D.
hearsAppealsBy
Indicates that one party has the authority or role to review and decide on appeals submitted by another party.
-
E.
previousHighestCourtOfAppeal
chosen
Indicates that one court previously served as the highest court of appeal for another jurisdiction or legal system.
- 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_69f76e4c1b248190b10667d0213537fe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fed357b2b4819084c709056a54461f |
completed | May 9, 2026, 6:25 a.m. |
| PD | Predicate disambiguation | batch_69fed103d9cc81909b11619745110c61 |
completed | May 9, 2026, 6:15 a.m. |
Created at: May 3, 2026, 4:09 p.m.