Triple
T8549373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuruntokai |
E202406
|
entity |
| Predicate | anonymousAuthorship |
P13269
|
FINISHED |
| Object | multiple poets |
—
|
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: multiple poets | Statement: [Kuruntokai, anonymousAuthorship, multiple poets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: anonymousAuthorship Context triple: [Kuruntokai, anonymousAuthorship, multiple poets]
-
A.
authorshipInitially
Indicates that an entity is the original or first author/creator of another entity before any subsequent authorship changes or contributions.
-
B.
publishedAnonymously
chosen
Indicates that a work was made public without revealing the identity of its creator or author.
-
C.
pseudonymousAttribution
Indicates that an action, work, or statement is attributed to an entity using a pseudonym rather than their real identity.
-
D.
authorshipStatus
Indicates the current state or condition of an entity’s role as an author in relation to a work (e.g., confirmed, disputed, anonymous, or pending).
-
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_69ca832610e08190b3b6c6cd2c250255 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe753d3608190b0573477182cf194 |
completed | March 31, 2026, 3:25 p.m. |
| PD | Predicate disambiguation | batch_69cbd113e05c81908f4f3fc1b5925164 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:19 p.m.