Triple
T30497067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | preliminary rulings of Court of Justice of the European Union |
E776034
|
entity |
| Predicate | canConcern |
P11116
|
FINISHED |
| Object | interpretation of EU treaties |
—
|
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: interpretation of EU treaties | Statement: [preliminary rulings of Court of Justice of the European Union, canConcern, interpretation of EU treaties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canConcern Context triple: [preliminary rulings of Court of Justice of the European Union, canConcern, interpretation of EU treaties]
-
A.
concern
chosen
Indicates that one entity is about, relates to, or is of interest or importance to another entity.
-
B.
concernedSee
Indicates that one entity looks at or observes another with a sense of worry, care, or concern.
-
C.
raisedConcernAbout
Indicates that one entity has expressed worry, doubt, or objection regarding another entity or issue.
-
D.
subjectOfConcernFor
Indicates that one entity is regarded as a matter of worry, interest, or attention for another entity.
-
E.
concernedActivity
Indicates that one entity is related to, involved in, or affected by a particular activity or action.
- 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_69f22498c5d481908aaea89e6fab8280 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6877cce40819096c86a4b738e4bed |
completed | May 2, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_69f678d2196c8190b9d0d2fcd47cc539 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:14 p.m.