Triple
T3122247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | She Don’t Really Care_1 Luv |
E65209
|
entity |
| Predicate | hasPrimaryCreatorRole |
P14496
|
FINISHED |
| Object | singer-songwriter |
—
|
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: singer-songwriter | Statement: [She Don’t Really Care_1 Luv, hasPrimaryCreatorRole, singer-songwriter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryCreatorRole Context triple: [She Don’t Really Care_1 Luv, hasPrimaryCreatorRole, singer-songwriter]
-
A.
hasPrimaryMaintainer
Indicates that one entity is the main person or organization responsible for maintaining or overseeing another entity.
-
B.
hasMainRole
chosen
Indicates that an entity holds the primary or most significant role in relation to another entity or context.
-
C.
hasProductionRole
Indicates that an entity holds a specific role or function in the production or creation process of another entity.
-
D.
createdBy
Indicates that something was brought into existence, produced, or authored through the actions or efforts of a specific agent or entity.
-
E.
hasAuthor
Indicates that an entity is written or created by a specific author.
- 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_69ad8580c72481909672d37acf647893 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada52ab05c819088204bbb608c837c |
completed | March 8, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69ad9df62e548190b053e1478deed467 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:04 p.m.