Triple
T24408447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premio FIL de Literatura en Lenguas Romances |
E615376
|
entity |
| Predicate | alcance |
P45893
|
FINISHED |
| Object | mundo hispano y lusófono |
—
|
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: mundo hispano y lusófono | Statement: [Premio FIL de Literatura en Lenguas Romances, alcance, mundo hispano y lusófono]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alcance Context triple: [Premio FIL de Literatura en Lenguas Romances, alcance, mundo hispano y lusófono]
-
A.
tieneAlcance
chosen
Indicates that something possesses or has a certain scope, reach, or range of effect in relation to something else.
-
B.
reaches
Indicates that one entity extends or moves until it makes contact with, attains, or arrives at another entity or point.
-
C.
maximumReach
Indicates the greatest extent, distance, or limit that something can reach or influence within a given context.
-
D.
range
Indicates that a value, property, or effect extends between specified limits or over a specified interval or scope.
-
E.
canReach
Indicates that one entity is able to access, arrive at, or establish a path to 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_69e2d7e780bc81908049c779e697a7f6 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2957fab0481909121c6da6b5e34c0 |
completed | April 29, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:05 a.m.