Triple
T9164836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asad |
E219923
|
entity |
| Predicate | associatedWithPoeticPersona |
P77791
|
FINISHED |
| Object | romantic lover |
—
|
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: romantic lover | Statement: [Asad, associatedWithPoeticPersona, romantic lover]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithPoeticPersona Context triple: [Asad, associatedWithPoeticPersona, romantic lover]
-
A.
associatedWithPoem
Indicates a relationship in which an entity is connected or linked to a particular poem, such as by authorship, subject, reference, or contextual association.
-
B.
characterizesPoetAs
chosen
Indicates that one entity portrays, defines, or describes a poet in terms of particular qualities, roles, or attributes.
-
C.
usedByPoet
Indicates that something (such as a word, style, device, or object) is employed or utilized by a poet.
-
D.
poeticCategory
Indicates that one entity is classified as belonging to a particular poetic category or type of poetry in relation to another entity.
-
E.
poeticStyle
Indicates the stylistic or formal manner in which something is expressed in poetry, such as its structure, tone, and linguistic features.
- 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_69ca83e3633c81908688a9fa2306ba99 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccaa2ee64c8190a9a5abafe5d0b086 |
completed | April 1, 2026, 5:16 a.m. |
| PD | Predicate disambiguation | batch_69cc6605c6808190a30d92da006206ac |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:22 p.m.