Triple
T36671131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EGF |
E905418
|
entity |
| Predicate | applicationsSubmittedBy |
P200586
|
FINISHED |
| Object | EU Member States |
—
|
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: EU Member States | Statement: [EGF, applicationsSubmittedBy, EU Member States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: applicationsSubmittedBy Context triple: [EGF, applicationsSubmittedBy, EU Member States]
-
A.
applicantIn
Indicates that a person or entity is serving as an applicant within a particular context, process, or organization.
-
B.
onlineApplication
Indicates that an application or request is submitted, processed, or managed through an online or web-based system.
-
C.
applicationStatus
Indicates the current state or outcome of an application within its processing lifecycle.
-
D.
applicationProcessIncludes
Indicates that an application process contains or encompasses a specific step, component, or sub-process as part of its overall workflow.
-
E.
applicationFiledOn
Indicates that an application was formally submitted on a specific date or at a specific point in time.
- 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_69f76e6f10008190aea41746aa1b186e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff97637ad881908c24fe2cc6b036db |
completed | May 9, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69ff96c43a808190942eeda1934602db |
completed | May 9, 2026, 8:19 p.m. |
| PDg | Predicate description generation | batch_69ff976281888190a2e872296fb4a661 |
completed | May 9, 2026, 8:21 p.m. |
Created at: May 3, 2026, 4:12 p.m.