Triple
T20000498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bluets (stage adaptation) |
E494308
|
entity |
| Predicate | adaptationOfForm |
P97429
|
FINISHED |
| Object | lyric essay |
—
|
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: lyric essay | Statement: [Bluets (stage adaptation), adaptationOfForm, lyric essay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adaptationOfForm Context triple: [Bluets (stage adaptation), adaptationOfForm, lyric essay]
-
A.
adaptationType
Indicates the specific kind or category of adaptation that relates one entity to another or to a particular context.
-
B.
adaptationIn
Indicates that something appears, is represented, or takes place within a particular adaptation of an original work.
-
C.
adoptedInForm
chosen
Indicates that something is accepted, implemented, or brought into use within a particular form, format, or structural arrangement.
-
D.
adaptation
Indicates a relationship where one entity changes or is modified to better suit, function within, or correspond to another entity or context.
-
E.
mayAdapt
Indicates that one entity is permitted or allowed to modify, adjust, or alter 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e661a15f308190a99ac3205f948acb |
completed | April 20, 2026, 5:25 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:32 p.m.