Triple
T3992431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regulation (EU) No 1292/2013 |
E87021
|
entity |
| Predicate | bindingInItsEntirety |
P1045
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Regulation (EU) No 1292/2013, bindingInItsEntirety, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bindingInItsEntirety Context triple: [Regulation (EU) No 1292/2013, bindingInItsEntirety, true]
-
A.
binding
Indicates that one entity physically or chemically attaches, adheres, or forms a stable association with another entity.
-
B.
bindingOn
chosen
Indicates that one party is legally or formally obligated to follow, accept, or be governed by a decision, rule, or agreement established by another.
-
C.
heldTogetherWith
Indicates that two or more entities are physically joined or kept in contact by some binding, fastening, or cohesive force.
-
D.
bindsTo
Indicates that one entity physically or functionally attaches or connects to another, often with some specificity or selectivity in the interaction.
-
E.
boundFor
Indicates that something is destined, directed, or scheduled to go toward a particular destination or target.
- 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_69aed94118148190975e6aa4e554cde9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb81040481909b22e4c445ecae0f |
completed | March 9, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69aef8f692008190bf4d637ffc3d3eaa |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:33 p.m.