Triple
T29939189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Competition Act 1998 |
E760447
|
entity |
| Predicate | chapterIProhibitionTargets |
P272
|
FINISHED |
| Object | anti-competitive agreements |
—
|
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: anti-competitive agreements | Statement: [Competition Act 1998, chapterIProhibitionTargets, anti-competitive agreements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chapterIProhibitionTargets Context triple: [Competition Act 1998, chapterIProhibitionTargets, anti-competitive agreements]
-
A.
prohibitionActivity
Indicates that a certain activity is forbidden or not allowed to be performed.
-
B.
alcoholPolicy
Indicates the rules or restrictions governing the possession, sale, or consumption of alcohol in a given context.
-
C.
lawEnforcementTarget
Indicates that an entity is the focus or object of attention, investigation, or action by law enforcement authorities.
-
D.
censorshipTarget
Indicates that an entity is the object or focus of censorship by another entity or authority.
-
E.
prohibits
chosen
Indicates that one entity forbids or disallows another entity from performing a specific action or being in a certain state.
- 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_69f67805551c81909e016ae9e3031076 |
completed | May 2, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:21 p.m.