Triple
T36637952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ECRIS-TCN |
E904510
|
entity |
| Predicate | operationalManagementBy |
P99793
|
FINISHED |
| Object | eu-LISA |
E262393
|
NE 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: eu-LISA | Statement: [ECRIS-TCN, operationalManagementBy, eu-LISA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationalManagementBy Context triple: [ECRIS-TCN, operationalManagementBy, eu-LISA]
-
A.
managementIs
Indicates that one entity holds a managerial role, responsibility, or authority over another entity.
-
B.
resultsManagedBy
Indicates that the outcomes or results of a process, activity, or evaluation are overseen, controlled, or administered by a specified managing entity.
-
C.
managementController
chosen
Indicates that one entity serves as the management controller responsible for overseeing, configuring, or administering another entity.
-
D.
operationalSection
Indicates that a section or segment of a larger system, structure, or process is currently active and functioning as intended.
-
E.
operatesBy
Indicates that an entity performs its function, action, or process through the use or application of another entity (e.g., a method, mechanism, or principle).
- F. None of above.
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_6a01bb06422c819095bb42f6f3a0e801 |
completed | May 11, 2026, 11:18 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3c171a3dcc8190a3f582d4b13beff2 |
completed | June 24, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_6a01b9991c348190ac49b65ea2fd86ed |
completed | May 11, 2026, 11:12 a.m. |
Created at: May 3, 2026, 4:11 p.m.