Triple
T5450507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Instrucciones del Año XIII |
E122356
|
entity |
| Predicate | defiende |
P6876
|
FINISHED |
| Object | soberanía de los pueblos |
—
|
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: soberanía de los pueblos | Statement: [Instrucciones del Año XIII, defiende, soberanía de los pueblos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defiende Context triple: [Instrucciones del Año XIII, defiende, soberanía de los pueblos]
-
A.
defends
chosen
Indicates that one entity protects or supports another entity against attack, criticism, or harm.
-
B.
defender
Indicates a relationship where one entity protects, guards, or supports another entity against threats, attacks, or criticism.
-
C.
defenderIn
Indicates that an entity serves as a defensive agent or protector within a specified context, situation, or domain.
-
D.
defendedAs
Indicates that one entity is presented, argued, or justified as being equivalent to or serving the role of another entity in a defensive or protective context.
-
E.
defense
Indicates an action or relationship in which an entity protects, guards, or resists against a threat, attack, or criticism from another entity.
- 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_69bd4640f52c81909e653ec361f66d76 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd95be329c81908783420cf81b6af5 |
completed | March 20, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69bd919e8d18819098c4af6a015e5cc2 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:07 p.m.