Triple
T10341252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TFEU Article 101 |
E243131
|
entity |
| Predicate | listsExample |
P93781
|
FINISHED |
| Object | price fixing |
—
|
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: price fixing | Statement: [TFEU Article 101, listsExample, price fixing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: listsExample Context triple: [TFEU Article 101, listsExample, price fixing]
-
A.
listType
Indicates that one entity specifies the classification or category type of a list associated with another entity.
-
B.
listsMeans
Indicates that one entity enumerates or specifies the meaning, definition, or interpretation of another entity.
-
C.
listsGiant
Indicates that one entity enumerates or catalogs another entity that is characterized as a giant.
-
D.
listAPurpose
Indicates that an entity enumerates or specifies the purposes, goals, or intended uses associated with another entity.
-
E.
listsSecurity
Indicates that an entity specifies or enumerates security-related items, settings, or attributes associated with another entity.
- F. None of above. chosen
Provenance (4 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e91fdb2081909866c6ecf417d75a |
completed | April 7, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69d4df9dc3208190bf1bd106f44f6202 |
completed | April 7, 2026, 10:42 a.m. |
| PDg | Predicate description generation | batch_69d4e91ce2008190af252c140370b7f2 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, 11:55 a.m.