Triple
T36637751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | eu-LISA |
E904506
|
entity |
| Predicate | responsibleForSystem |
P636
|
FINISHED |
| Object | Schengen Information System (SIS) |
—
|
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: Schengen Information System (SIS) | Statement: [eu-LISA, responsibleForSystem, Schengen Information System (SIS)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: responsibleForSystem Context triple: [eu-LISA, responsibleForSystem, Schengen Information System (SIS)]
-
A.
responsibleFor
chosen
Indicates that one entity has a duty, obligation, or role to manage, oversee, or be accountable for another entity or outcome.
-
B.
partOfSystem
Indicates that one entity functions as a component or subsystem within the structure or organization of another entity.
-
C.
servedSystem
Indicates that one system has provided service, functionality, or resources to another system.
-
D.
worksWithinSystem
Indicates that an entity performs its functions or activities while operating inside a specified system, framework, or organizational structure.
-
E.
definesSystemAs
Indicates that one entity explicitly specifies or establishes another entity as the system to be used, referenced, or treated as authoritative.
- 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_69f76e6c63e48190b1d0c3a79a6c7406 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:11 p.m.