Triple
T25542571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goodnight n Go |
E640210
|
entity |
| Predicate | creditedInfluence |
P87217
|
FINISHED |
| Object | Imogen Heap |
—
|
NE NERFINISHED |
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: Imogen Heap | Statement: [Goodnight n Go, creditedInfluence, Imogen Heap]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creditedInfluence Context triple: [Goodnight n Go, creditedInfluence, Imogen Heap]
-
A.
influencedIn
Indicates that one entity had an effect on or shaped another entity within a specific context, domain, or setting.
-
B.
wereInfluencedBy
chosen
Indicates that one entity’s ideas, actions, or characteristics were shaped or affected by another entity.
-
C.
creditedIn
Indicates that an entity is acknowledged or listed as a contributor or source within a particular work, record, or context.
-
D.
awardsInfluenced
Indicates that one award has affected, shaped, or contributed to the creation, criteria, or significance of another award.
-
E.
creditedFor
Indicates that one entity is acknowledged as the source, contributor, or originator responsible for another entity (such as a work, achievement, or outcome).
- 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_69e75dbfff7081909b0aa779d48321d2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f895278881909c376fc06b290c56 |
completed | May 2, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 3:26 p.m.