Triple
T20385552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Standards repertoire |
E497947
|
entity |
| Predicate | includesTypeOfWork |
P86785
|
FINISHED |
| Object | love songs |
—
|
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: love songs | Statement: [Standards repertoire, includesTypeOfWork, love songs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesTypeOfWork Context triple: [Standards repertoire, includesTypeOfWork, love songs]
-
A.
associatedWorkType
chosen
Indicates the type or category of work with which an entity is associated (e.g., publication, artwork, performance).
-
B.
workIncludes
Indicates that a work (such as a project, document, or creative piece) contains or incorporates another specified component, part, or element.
-
C.
includedWorkOn
Indicates that one entity contains, features, or incorporates another entity as a work or component within it.
-
D.
hasSignificantWorkType
Indicates that an entity is associated with a primary or notably important type or category of work.
-
E.
typeOfWork
Indicates the kind or category of work associated with or performed by 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_69e0b4a71ebc8190b153a36c738730f4 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6790a31a4819099b2e6df2bafe547 |
completed | April 20, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69e57648be3c81908256838228cabf5c |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:28 a.m.