Triple
T34038179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Commission directorates-general |
E872865
|
entity |
| Predicate | hasDG |
P178164
|
FINISHED |
| Object | Directorate-General for Competition |
—
|
NE NERFINISHED |
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: Directorate-General for Competition | Statement: [European Commission directorates-general, hasDG, Directorate-General for Competition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDG Context triple: [European Commission directorates-general, hasDG, Directorate-General for Competition]
-
A.
hasDAC
Indicates that an entity includes, uses, or is equipped with a Digital-to-Analog Converter (DAC) component.
-
B.
hasSign
Indicates that an entity possesses, displays, or is associated with a particular sign or symbol.
-
C.
hasDUB
Indicates that one entity possesses or is associated with a deubiquitinating enzyme (DUB) activity or component.
-
D.
hasPar
Indicates a relationship where one entity has another entity as its parent.
-
E.
hasDOC
Indicates that one entity is associated with, linked to, or possesses a specific document or documentation.
- 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_69f349a3363081909cea4c9a848cefe2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70c53062c8190b4cb7be22ab00bc7 |
completed | May 3, 2026, 8:50 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70b94784c8190970d654e066eb50d |
completed | May 3, 2026, 8:47 a.m. |
Created at: May 1, 2026, 1:51 a.m.