Triple
T22879304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Codice dei beni culturali e del paesaggio |
E567415
|
entity |
| Predicate | entrataInVigore |
P98493
|
FINISHED |
| Object | 1 maggio 2004 |
—
|
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: 1 maggio 2004 | Statement: [Codice dei beni culturali e del paesaggio, entrataInVigore, 1 maggio 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entrataInVigore Context triple: [Codice dei beni culturali e del paesaggio, entrataInVigore, 1 maggio 2004]
-
A.
activeAt
chosen
Indicates that an entity is functioning, valid, or in effect during a specified time or at a particular location or context.
-
B.
entersBy
Indicates that one entity moves into or gains access to another entity through a specified entrance, route, or means.
-
C.
enteredInto
Indicates that one entity has initiated or become formally involved in a particular state, agreement, relationship, or situation with another entity.
-
D.
hasEntranceOn
Indicates that one entity’s entrance or access point is located on or faces a specified side, boundary, or feature of another entity.
-
E.
activeAs
Indicates that an entity is currently functioning or serving in a particular role, capacity, or status.
- 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_69e24589d8348190b96422d13a678bc1 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17f5b1ea481909a31a8ed6792ad04 |
completed | April 29, 2026, 3:47 a.m. |
| PD | Predicate disambiguation | batch_69ef3b6b2e2481908258156937b5a745 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:39 p.m.