Triple
T33559236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article 148 of the Treaty on the Functioning of the European Union |
E859565
|
entity |
| Predicate | titleOfTitle |
P198708
|
FINISHED |
| Object | Employment |
—
|
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: Employment | Statement: [Article 148 of the Treaty on the Functioning of the European Union, titleOfTitle, Employment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleOfTitle Context triple: [Article 148 of the Treaty on the Functioning of the European Union, titleOfTitle, Employment]
-
A.
titles
Indicates that one entity holds a formal title, designation, or name associated with another entity.
-
B.
title
Indicates that one entity serves as the formal name or designation of another entity.
-
C.
titleAffirms
Indicates that a title explicitly asserts, confirms, or supports the truth or validity of a particular claim, idea, or relationship.
-
D.
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.
-
E.
titleInEnglish
Indicates that an entity’s title or name is given in the English language.
- 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_69f3497b2b68819093207971b5e13dc8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69feff70fbec8190b1ff5f943f29613e |
completed | May 9, 2026, 9:33 a.m. |
| PD | Predicate disambiguation | batch_69fefbcd5b7881909cfe52b32f8a4301 |
completed | May 9, 2026, 9:18 a.m. |
| PDg | Predicate description generation | batch_69feff703fec8190ab7d0633e0cc5459 |
completed | May 9, 2026, 9:33 a.m. |
Created at: May 1, 2026, 1:40 a.m.