Triple
T33514027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article 121 TFEU |
E858317
|
entity |
| Predicate | titleHeading |
P198632
|
FINISHED |
| Object | Economic and monetary policy |
—
|
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: Economic and monetary policy | Statement: [Article 121 TFEU, titleHeading, Economic and monetary policy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleHeading Context triple: [Article 121 TFEU, titleHeading, Economic and monetary policy]
-
A.
title
Indicates that one entity serves as the formal name or designation of another entity.
-
B.
titleOver
Indicates that one entity holds a formal title, rank, or designation in relation to another entity, often implying authority, status, or role over it.
-
C.
titleStart
Indicates that one entity’s title begins with the text or substring represented by the other entity.
-
D.
titleVariant
Indicates that one title is an alternative or variant form of another title referring to the same work or entity.
-
E.
titleThrough
Indicates a relationship where one entity holds or is identified by a specific title by means of, or via the mediation of, another entity or context.
- 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_69f3497721848190978fbee5e0a526f8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fef8c3f2388190b995ec173512945a |
completed | May 9, 2026, 9:05 a.m. |
| PD | Predicate disambiguation | batch_69fef65975608190960b78d27e806d4f |
completed | May 9, 2026, 8:54 a.m. |
| PDg | Predicate description generation | batch_69fef8c2cdd881908c6f44e4dfa5ffd0 |
completed | May 9, 2026, 9:05 a.m. |
Created at: May 1, 2026, 1:39 a.m.