Triple
T5973418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Board of Supervisors (EIOPA) |
E132927
|
entity |
| Predicate | supervisesSector |
P9418
|
FINISHED |
| Object | insurance |
—
|
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: insurance | Statement: [Board of Supervisors (EIOPA), supervisesSector, insurance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supervisesSector Context triple: [Board of Supervisors (EIOPA), supervisesSector, insurance]
-
A.
ownerSector
Indicates the sector or industry category to which the owner of an entity belongs.
-
B.
observedBySector
Indicates that something (such as an event, object, or phenomenon) is monitored, detected, or recorded by a specific sector or segment.
-
C.
canSupervise
chosen
Indicates that one entity has the authority or capability to oversee, direct, or manage the work or activities of another entity.
-
D.
sectorServed
Indicates the industry or economic sector that an entity primarily serves or targets with its activities, products, or services.
-
E.
oversee
Indicates having responsibility for supervising, directing, or managing the actions or work of another entity.
- 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_69c0086deab081908550159ca23eec9b |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04dc2243c8190bd3488e7b24af985 |
completed | March 22, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69c049dcb3c081908ccc9b4d4b210229 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:03 p.m.