Triple
T29939265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enterprise Act 2002 |
E760448
|
entity |
| Predicate | establishesAppealBody |
P7724
|
FINISHED |
| Object | Competition Appeal Tribunal |
—
|
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: Competition Appeal Tribunal | Statement: [Enterprise Act 2002, establishesAppealBody, Competition Appeal Tribunal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishesAppealBody Context triple: [Enterprise Act 2002, establishesAppealBody, Competition Appeal Tribunal]
-
A.
appellateBodyFound
Indicates that an appellate body has reached and recorded a decision or finding regarding a prior judgment or ruling.
-
B.
establishedBody
chosen
Indicates that an entity created, founded, or formally set up another entity, such as an organization, institution, or governing body.
-
C.
hearsAppealTo
Indicates that one entity formally reviews and considers an appeal submitted by another entity.
-
D.
decisionSubjectToAppealOn
Indicates that a particular decision is open to being challenged or reviewed through an appeal process.
-
E.
centralAppeal
Indicates that something serves as the main attraction, focus, or compelling feature that draws interest or attention.
- 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_69f22463f3648190a603c3ff305c660b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 29, 2026, 6:21 p.m.