Triple
T10341737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eurodac system |
E243141
|
entity |
| Predicate | storesForPurpose |
P93786
|
FINISHED |
| Object | asylum procedure management |
—
|
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: asylum procedure management | Statement: [Eurodac system, storesForPurpose, asylum procedure management]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storesForPurpose Context triple: [Eurodac system, storesForPurpose, asylum procedure management]
-
A.
storesInterfaceIn
Indicates that one entity keeps or maintains an interface definition within another entity (such as a container, module, or storage location).
-
B.
storesConfigurationFor
Indicates that one entity holds or maintains configuration settings that are used by or apply to another entity.
-
C.
storeType
Indicates the category or kind of store associated with an entity, such as its retail or service type.
-
D.
store
Indicates that one entity keeps or holds another entity in a place or system for future use or access.
-
E.
storesIndexesIn
Indicates that one entity maintains and holds index data within another storage entity or system.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e91fdb2081909866c6ecf417d75a |
completed | April 7, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69d4df9dc3208190bf1bd106f44f6202 |
completed | April 7, 2026, 10:42 a.m. |
| PDg | Predicate description generation | batch_69d4e91ce2008190af252c140370b7f2 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, 11:55 a.m.