Triple
T23909367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abstract Poetic |
E601293
|
entity |
| Predicate | bearerNotableSoloWorkOfBearer |
P93727
|
FINISHED |
| Object | Amplified |
—
|
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: Amplified | Statement: [Abstract Poetic, bearerNotableSoloWorkOfBearer, Amplified]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bearerNotableSoloWorkOfBearer Context triple: [Abstract Poetic, bearerNotableSoloWorkOfBearer, Amplified]
-
A.
authorNotableWork
Indicates that a person is the creator or writer of a specific notable work, such as a book, article, or other significant publication.
-
B.
hasArtistOfNotableWork
Indicates that an entity is associated with the artist who created a notable work related to that entity.
-
C.
namedForNotableWork
Indicates that one entity is named in honor of another entity’s notable work or achievement.
-
D.
notableWorkSubject
Indicates that a work is notably associated with a particular subject, such as a person, topic, or entity, as its primary focus or theme.
-
E.
notableWorkAs
chosen
Indicates a relationship where a particular work is recognized as a significant or distinguished creation associated with an 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_69e295364a488190bcac702e9bb7f764 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1ce93a20c8190b1c8170d955c8d96 |
completed | April 29, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:38 p.m.