Triple
T752955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nueva gramática de la lengua española |
E15489
|
entity |
| Predicate | cubre |
P13946
|
FINISHED |
| Object | morfología del español |
—
|
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: morfología del español | Statement: [Nueva gramática de la lengua española, cubre, morfología del español]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cubre Context triple: [Nueva gramática de la lengua española, cubre, morfología del español]
-
A.
alsoCovers
chosen
Indicates that something extends its scope or applicability to include an additional subject, area, or case beyond what was originally covered.
-
B.
bodyCovering
Indicates the type of external covering or surface (such as skin, fur, feathers, or scales) that characterizes an entity’s body.
-
C.
partlyCoveredBy
Indicates that one entity is covered or overlapped by another entity, but only to a partial extent rather than completely.
-
D.
hasCoverType
Indicates that one entity possesses or is associated with a specific type or category of cover.
-
E.
caps
Indicates that one entity serves as the capital city or administrative center of another entity, such as a country, state, or region.
- 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_69a493599a0081908da65f3407af1ef2 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a64d7d2c8190a6059adcb8fbd34f |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a501c4cc81908de6d63e3d4f60d7 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.