Triple
T3769927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Single Supervisory Mechanism |
E82771
|
entity |
| Predicate | coversSector |
P5037
|
FINISHED |
| Object | banking sector |
—
|
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: banking sector | Statement: [Single Supervisory Mechanism, coversSector, banking sector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversSector Context triple: [Single Supervisory Mechanism, coversSector, banking sector]
-
A.
coversSection
Indicates that one entity includes, addresses, or provides content for a particular section of another entity.
-
B.
coversField
Indicates that one entity extends over, protects, or occupies the surface or area of a field associated with another entity.
-
C.
coversPolicyArea
chosen
Indicates that a policy, document, or initiative includes or addresses a particular policy area or topic within its scope.
-
D.
sectorServed
Indicates the industry or economic sector that an entity primarily serves or targets with its activities, products, or services.
-
E.
observedBySector
Indicates that something (such as an event, object, or phenomenon) is monitored, detected, or recorded by a specific sector or segment.
- 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_69ad8b207b0081909d2b48843fbd8795 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcc2f016c81909c2e3c85dbc3c259 |
completed | March 8, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69adc04ec36c8190bd5b944d4f4d32aa |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:35 p.m.