Triple
T21692176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Tyger |
E535396
|
entity |
| Predicate | questioningStyle |
P126962
|
FINISHED |
| Object | series of rhetorical questions |
—
|
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: series of rhetorical questions | Statement: [The Tyger, questioningStyle, series of rhetorical questions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: questioningStyle Context triple: [The Tyger, questioningStyle, series of rhetorical questions]
-
A.
questionStyle
chosen
Indicates the manner or format in which a question is posed or expressed.
-
B.
interrogationMethod
Indicates the technique or approach used by one party to question or extract information from another.
-
C.
guidingQuestionOf
Indicates that one item serves as a guiding or central question that frames, directs, or structures another item (such as a discussion, activity, or work).
-
D.
discussionStyle
Indicates the manner or approach with which one party conducts or participates in a discussion with another.
-
E.
typicalDialogueStyle
Indicates the characteristic manner or pattern in which an entity typically communicates or conducts dialogue.
- 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_69e0c46a6ee481908836e1420fb78c9b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef96d0d4048190abfc3e3e06c51b8d |
completed | April 27, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69e6969113cc8190ab69855ef5667e4b |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:45 p.m.