Triple
T8050751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UK–EU Joint Committee |
E187665
|
entity |
| Predicate | disputeSettlementMechanism |
P6659
|
FINISHED |
| Object | consultations between the parties |
—
|
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: consultations between the parties | Statement: [UK–EU Joint Committee, disputeSettlementMechanism, consultations between the parties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disputeSettlementMechanism Context triple: [UK–EU Joint Committee, disputeSettlementMechanism, consultations between the parties]
-
A.
disputeSettlementArm
Indicates a relationship where an entity functions as the division, branch, or mechanism responsible for handling, managing, or resolving disputes or conflicts for another entity.
-
B.
methodOfDisputeResolution
chosen
Indicates the process or mechanism used to settle a disagreement or conflict between parties.
-
C.
resolutionMechanism
Indicates the method, process, or system used to resolve a conflict, issue, or discrepancy between entities.
-
D.
disputeSettlementNumber
Indicates the identifying number assigned to a specific dispute settlement case or process.
-
E.
disputeResolvedIn
Indicates that a particular dispute has been settled or resolved within a specified location, forum, or jurisdiction.
- 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_69ca82b15e948190a62fd7af5218426a |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3f799d1481909c91039941af0e34 |
completed | March 31, 2026, 3:28 a.m. |
| PD | Predicate disambiguation | batch_69cb049a1b9c8190811c396421ebf9c9 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:24 p.m.