Triple
T10341791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prüm Decisions |
E243142
|
entity |
| Predicate | hasImplementationInstrument |
P19961
|
FINISHED |
| Object | national implementing legislation in member states |
—
|
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: national implementing legislation in member states | Statement: [Prüm Decisions, hasImplementationInstrument, national implementing legislation in member states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImplementationInstrument Context triple: [Prüm Decisions, hasImplementationInstrument, national implementing legislation in member states]
-
A.
hasTypeOfInstrumentation
Indicates that one entity uses, involves, or is characterized by a particular type of instrumentation.
-
B.
hasImplementationDetail
chosen
Indicates that one entity specifies or contains a concrete implementation detail or internal mechanism related to another entity.
-
C.
hasStandardImplementation
Indicates that an entity has a defined, commonly accepted implementation that follows an established standard or specification.
-
D.
canBeImplementedWith
Indicates that one entity is capable of being realized, executed, or fulfilled through the use or application of another entity.
-
E.
supportsDynamicInstrumentation
Indicates that an entity is capable of being instrumented or monitored at runtime without requiring recompilation or restart.
- 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_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. |
Created at: April 6, 2026, 11:55 a.m.