Triple
T34135438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | archpriest of Hita |
E875554
|
entity |
| Predicate | authorialIdentity |
P58922
|
FINISHED |
| Object | often identified with Juan Ruiz |
—
|
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: often identified with Juan Ruiz | Statement: [archpriest of Hita, authorialIdentity, often identified with Juan Ruiz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorialIdentity Context triple: [archpriest of Hita, authorialIdentity, often identified with Juan Ruiz]
-
A.
authorialSource
Indicates that one entity serves as the originating author or creator of the content, work, or information associated with another entity.
-
B.
authorshipInFiction
Indicates that one entity is the creator or writer of a fictional work in which another entity appears or is represented.
-
C.
authorStyle
Indicates the stylistic characteristics or manner of expression associated with a particular author in their works.
-
D.
canonicalAuthor
chosen
Indicates that an entity is the officially recognized or standard author of a given work or resource.
-
E.
authorOfStyle
Indicates that an entity is the creator or originator of a particular style, method, or artistic approach.
- 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_69f349aaeef08190a20e72a3fdeb7052 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
Created at: May 1, 2026, 1:53 a.m.