Triple
T3388590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eurosystem |
E71361
|
entity |
| Predicate | supervisoryRole |
P10797
|
FINISHED |
| Object | supports the Single Supervisory Mechanism |
—
|
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: supports the Single Supervisory Mechanism | Statement: [Eurosystem, supervisoryRole, supports the Single Supervisory Mechanism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supervisoryRole Context triple: [Eurosystem, supervisoryRole, supports the Single Supervisory Mechanism]
-
A.
canSupervise
Indicates that one entity has the authority or capability to oversee, direct, or manage the work or activities of another entity.
-
B.
servesRole
Indicates that one entity performs, fulfills, or occupies a particular function, position, or responsibility in relation to another entity.
-
C.
supportsRole
chosen
Indicates that one entity provides the necessary functionality, resources, or conditions for another entity to perform or occupy a specific role.
-
D.
presidingRole
Indicates that one entity holds an official position of authority or leadership over a proceeding, organization, or event involving another entity.
-
E.
successorInSomeRoles
Indicates that one entity has taken over or followed another entity in certain specified roles or positions.
- 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_69ad85a8fd9c819095ecedf838d2bf1b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb665c6008190b33994ef20f5bd61 |
completed | March 8, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69ada43615f08190ac2275020d157983 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:14 p.m.