Triple
T14061821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yassa legal code (attributed) |
E338363
|
entity |
| Predicate | attributedAuthorRole |
P86337
|
FINISHED |
| Object | supreme khan |
—
|
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: supreme khan | Statement: [Yassa legal code (attributed), attributedAuthorRole, supreme khan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attributedAuthorRole Context triple: [Yassa legal code (attributed), attributedAuthorRole, supreme khan]
-
A.
authorAsCredited
Indicates the relationship between a work and the person or entity credited as its author, regardless of actual authorship.
-
B.
declaredRoleOfAuthor
chosen
Indicates that a specific role or capacity has been explicitly stated or assigned to an author in relation to a work or contribution.
-
C.
authorTraditionallyAscribedTo
Indicates that authorship of a work is customarily or historically attributed to an entity, even if definitive proof of authorship may be uncertain or disputed.
-
D.
associatedWithAuthorRole
Indicates that an entity is connected to another entity specifically in the capacity or role of an author.
-
E.
authorOfWorkAppearingIn
Indicates that one entity is the creator or writer of a work that appears within another work or publication.
- 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_69d81c67ba6c819091935650dfb3b895 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de568876308190840361dcaf10bd45 |
completed | April 14, 2026, 3 p.m. |
| PD | Predicate disambiguation | batch_69de05adef888190b023ab42ef5076b6 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:21 p.m.