Triple
T27931121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tribunals of England and Wales |
E707983
|
entity |
| Predicate | resolvesDisputesIn |
P6660
|
FINISHED |
| Object | asylum law |
—
|
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: asylum law | Statement: [tribunals of England and Wales, resolvesDisputesIn, asylum law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resolvesDisputesIn Context triple: [tribunals of England and Wales, resolvesDisputesIn, asylum law]
-
A.
disputeResolvedIn
Indicates that a particular dispute has been settled or resolved within a specified location, forum, or jurisdiction.
-
B.
handlesDisputesOver
chosen
Indicates that one entity is responsible for managing, resolving, or adjudicating disputes concerning another entity.
-
C.
disputeResolvedBy
Indicates that a particular dispute or conflict has been settled or resolved through the actions, decision, or intervention of a specified party or process.
-
D.
hasDisputeWith
Indicates that there is a conflict, disagreement, or contested issue between two entities.
-
E.
numberOfDisputations
Indicates the quantity of disputations (formal debates or arguments) associated with an entity.
- 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_69ef96bbf2c48190a9d0e0291457aab6 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 7:03 p.m.