Triple
T24950601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ensaios de Poesia Brasileira |
E624322
|
entity |
| Predicate | literaryDiscipline |
P97423
|
FINISHED |
| Object | poetics |
—
|
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: poetics | Statement: [Ensaios de Poesia Brasileira, literaryDiscipline, poetics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: literaryDiscipline Context triple: [Ensaios de Poesia Brasileira, literaryDiscipline, poetics]
-
A.
literarySubject
Indicates that one entity serves as the subject, topic, or focus of a literary work created by another entity.
-
B.
inLiterature
Indicates that a work, concept, or entity is mentioned, discussed, or represented within a piece of literature.
-
C.
literaryLanguage
Indicates that an entity is expressed, written, or communicated using a particular literary or standardized written language.
-
D.
literaryGenreOfWork
Indicates that a work belongs to or is classified under a particular literary genre.
-
E.
fieldOfWriting
chosen
Indicates that one entity is the domain, genre, or subject area in which another entity writes or produces written work.
- 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_69e2ff22e4c48190a0444b5a044f14e8 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 18, 2026, 5:56 a.m.