Triple
T3981979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DLE |
E85777
|
entity |
| Predicate | authorityOn |
P35765
|
FINISHED |
| Object | standard Spanish vocabulary |
—
|
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: standard Spanish vocabulary | Statement: [DLE, authorityOn, standard Spanish vocabulary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorityOn Context triple: [DLE, authorityOn, standard Spanish vocabulary]
-
A.
authorityGranted
Indicates that one entity has formally given another entity the power, rights, or permission to act or make decisions, typically within a defined scope or context.
-
B.
authorizedOn
Indicates that an entity has been granted official permission or rights to act, access, or operate on a specified object, resource, or context.
-
C.
usesAuthorityOf
Indicates that one entity exercises power, rights, or influence derived from or on behalf of another entity’s authority.
-
D.
authority
Indicates that one entity has the power, right, or official capacity to direct, control, or make decisions for another entity or over a particular domain.
-
E.
indicatesAuthorityOver
chosen
Indicates that one entity holds recognized power, control, or decision-making authority over 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_69aed93908348190a26c8aaf4fab3e86 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefa3ef7ac8190abe02f440ff83c43 |
completed | March 9, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69aef8f492ac819089dbb9436dbcdd2b |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:33 p.m.