Triple
T36637848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ETIAS |
E904508
|
entity |
| Predicate | responsibleInstitution |
P186218
|
FINISHED |
| Object | European Commission |
—
|
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: European Commission | Statement: [ETIAS, responsibleInstitution, European Commission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: responsibleInstitution Context triple: [ETIAS, responsibleInstitution, European Commission]
-
A.
sponsoringInstitution
Indicates that an institution provides financial or organizational support to enable or underwrite an activity, project, event, or entity.
-
B.
maintainedInstitution
Indicates that one entity is responsible for operating, supporting, or keeping another institution in working order over time.
-
C.
sourceInstitution
Indicates the institution from which something (such as a person, item, or record) originates or is issued.
-
D.
inInstitution
Indicates that an entity is located within, belongs to, or is formally associated with a particular institution.
-
E.
developedInstitution
Indicates that an entity played a primary role in creating, establishing, or significantly advancing an institution.
- 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_69f76e6c63e48190b1d0c3a79a6c7406 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7cabacc1481909e839454ce1057f7 |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7c9f4c7c48190ba918d8d5dc8dfd9 |
completed | May 3, 2026, 10:19 p.m. |
Created at: May 3, 2026, 4:11 p.m.