Triple
T4801090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ley de Sucesión en la Jefatura del Estado |
E106832
|
entity |
| Predicate | permiteDesignar |
P18722
|
FINISHED |
| Object | rey |
—
|
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: rey | Statement: [Ley de Sucesión en la Jefatura del Estado, permiteDesignar, rey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: permiteDesignar Context triple: [Ley de Sucesión en la Jefatura del Estado, permiteDesignar, rey]
-
A.
canBeDesignatedBy
Indicates that one entity is capable of being assigned, labeled, or identified by another entity as its designation.
-
B.
exportDesignation
Indicates that something is assigned a specific status or classification for export-related purposes, such as regulatory, legal, or logistical handling.
-
C.
designatesAuthority
Indicates that one entity formally assigns or confers decision-making power or control over something to another entity.
-
D.
designationFor
Indicates that one entity serves as the official title, label, or role name assigned to another entity.
-
E.
designationAct
chosen
Indicates an official act by which an authority formally assigns, names, or appoints an entity to a specific role, status, or function.
- 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_69bd43f6a1e08190bf0a372bfc336ee5 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c1c43a48190a65e56b1624a2339 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:23 p.m.