Triple
T8233436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Real Decreto 416/2006 |
E192346
|
entity |
| Predicate | hasFinalProvision |
P11051
|
FINISHED |
| Object | disposición final |
—
|
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: disposición final | Statement: [Real Decreto 416/2006, hasFinalProvision, disposición final]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFinalProvision Context triple: [Real Decreto 416/2006, hasFinalProvision, disposición final]
-
A.
hasFinalDecisionOn
Indicates that one entity holds the ultimate authority or responsibility to make and enforce a conclusive decision regarding another entity or matter.
-
B.
hasFinalStage
Indicates that an entity possesses or reaches a concluding or ultimate phase in a process, sequence, or lifecycle.
-
C.
hasProvisionOn
chosen
Indicates that one entity contains, specifies, or includes a particular provision, clause, or stipulation concerning another entity or subject.
-
D.
hasFinalMatch
Indicates that an entity is associated with a concluding or decisive match in a series, tournament, or competition.
-
E.
hasConclusion
Indicates that something leads to, results in, or is associated with a particular conclusion.
- 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_69ca82db5b90819085d1ad7c2e27bfcc |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb782792a48190a34b0abfcc92064b |
completed | March 31, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69cb36b1dea0819091418072501e79c1 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:46 p.m.