Triple
T27100716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epigrams |
E686430
|
entity |
| Predicate | associatedAuthorRole |
P84740
|
FINISHED |
| Object | court poet |
—
|
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: court poet | Statement: [Epigrams, associatedAuthorRole, court poet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedAuthorRole Context triple: [Epigrams, associatedAuthorRole, court poet]
-
A.
associatedWithAuthorRole
chosen
Indicates that an entity is connected to another entity specifically in the capacity or role of an author.
-
B.
artifactRole
Indicates the specific function, purpose, or responsibility that an artifact has within a particular context or activity.
-
C.
notableAuthorRole
Indicates that an entity holds a significant or distinguished role as an author in relation to another entity.
-
D.
declaredRoleOfAuthor
Indicates that a specific role or capacity has been explicitly stated or assigned to an author in relation to a work or contribution.
-
E.
hasContributorRoleOfAuthor
Indicates that an entity participates as a contributor specifically in the role of an author in relation to 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_69ef1489f8b481908e24a1985982bd26 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69ffb69812808190a751853b30183e65 |
completed | May 9, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69ffb63bdda88190a9dd8426dc0bad43 |
completed | May 9, 2026, 10:33 p.m. |
Created at: April 27, 2026, 8:47 a.m.