Triple
T9431360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Los trabajos de Persiles y Sigismunda |
E227381
|
entity |
| Predicate | authorClaimedAs |
P34338
|
FINISHED |
| Object | Cervantes’s best work |
—
|
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: Cervantes’s best work | Statement: [Los trabajos de Persiles y Sigismunda, authorClaimedAs, Cervantes’s best work]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorClaimedAs Context triple: [Los trabajos de Persiles y Sigismunda, authorClaimedAs, Cervantes’s best work]
-
A.
claimedAs
chosen
Indicates that one entity asserts ownership, authorship, responsibility, or some other form of association over another entity.
-
B.
authorBelongsTo
Indicates that an author is affiliated with, or is a member of, a particular organization, group, or entity.
-
C.
authorSameAs
Indicates that two author identifiers or representations refer to the same underlying author.
-
D.
authorOfDescription
Indicates that an entity is the creator or writer of a particular description or explanatory text about something.
-
E.
canonicalAuthor
Indicates that an entity is the officially recognized or standard author of a given work or resource.
- 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_69ca8437a7ac81908651de48f2d2141d |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd7e6059bc8190a7e98aef3caabd0b |
completed | April 1, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69cca55548488190b171ae695a3212de |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:49 p.m.