Triple
T18803543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Act against Restraints of Competition |
E459815
|
entity |
| Predicate | appliesAlongside |
P70805
|
FINISHED |
| Object | EU competition rules |
—
|
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: EU competition rules | Statement: [Act against Restraints of Competition, appliesAlongside, EU competition rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesAlongside Context triple: [Act against Restraints of Competition, appliesAlongside, EU competition rules]
-
A.
passedAlongside
Indicates that one entity moved or traveled next to another entity along the same route or path, maintaining a roughly parallel course.
-
B.
appliesAlsoTo
chosen
Indicates that a condition, rule, or characteristic that applies to one entity is additionally applicable to another entity.
-
C.
executedAlongWith
Indicates that one entity was carried out, performed, or implemented in conjunction with another entity, at the same time or as part of the same operation or event.
-
D.
administeredAlongside
Indicates that one treatment, drug, or intervention is given or applied at the same time as another.
-
E.
appliesAcross
Indicates that a condition, rule, or property holds uniformly over multiple items, cases, or contexts.
- 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_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a0253f748190998995e3b1524357 |
completed | April 20, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:53 a.m.