Triple
T26338401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dialectical Lyric |
E662577
|
entity |
| Predicate | hasModeOfPresentation |
P102437
|
FINISHED |
| Object | first-person reflection |
—
|
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: first-person reflection | Statement: [Dialectical Lyric, hasModeOfPresentation, first-person reflection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModeOfPresentation Context triple: [Dialectical Lyric, hasModeOfPresentation, first-person reflection]
-
A.
hasPresentation
Indicates that an entity delivers, contains, or is associated with a specific presentation (such as a talk, slide deck, or formal display of information).
-
B.
hasExhibitFormat
Indicates the specific format or medium in which an exhibit is presented or made available.
-
C.
presentedInFormat
chosen
Indicates that something is expressed, delivered, or made available using a particular format or representation.
-
D.
presentedIn
Indicates that something is shown, displayed, or formally introduced within a particular context, medium, event, or setting.
-
E.
hasArtFormPresented
Indicates that an entity presents, showcases, or features a particular art form.
- 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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 26, 2026, 10:37 p.m.