Triple
T4553441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trife |
E120422
|
entity |
| Predicate | hasCreativeWorkType |
P42896
|
FINISHED |
| Object | music recordings |
—
|
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: music recordings | Statement: [Trife, hasCreativeWorkType, music recordings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCreativeWorkType Context triple: [Trife, hasCreativeWorkType, music recordings]
-
A.
hasWrittenWorkType
Indicates that an entity (typically a written work) is associated with a specific type or category of written work (such as novel, article, report, etc.).
-
B.
creativeWorkType
chosen
Indicates the specific category or form of a creative work (such as book, movie, painting, or song) that characterizes the relationship.
-
C.
workTypeContributedTo
Indicates that an entity contributed to the creation, development, or production of a particular type of work.
-
D.
notableTypeOfWork
Indicates that a work is a significant or defining example within a particular type or category of work associated with an entity.
-
E.
hasFictionalWork
Indicates that one entity is the creator, owner, or source of a fictional work associated with 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_69bd4636f1648190a701445c2fcd9c17 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd581160e08190b715a8ce5c3e6c9b |
completed | March 20, 2026, 2:22 p.m. |
| PD | Predicate disambiguation | batch_69bd5223423c81908317351b58cff5f5 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:09 p.m.