Triple
T30556206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | There Goes the Neighborhood |
E777704
|
entity |
| Predicate | producerBestKnownForWorkingWith |
P113700
|
FINISHED |
| Object | Eagles |
—
|
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: Eagles | Statement: [There Goes the Neighborhood, producerBestKnownForWorkingWith, Eagles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: producerBestKnownForWorkingWith Context triple: [There Goes the Neighborhood, producerBestKnownForWorkingWith, Eagles]
-
A.
producerOftenWorkedWith
chosen
Indicates that a producer frequently collaborated or worked together with a particular entity (such as an artist, director, or production team) on multiple projects.
-
B.
musicalCollaborator
Indicates a relationship where two or more entities work together in creating, performing, or producing music.
-
C.
producerArtist
Indicates that one entity serves as the producer (e.g., overseeing or managing the creation) of a work created or performed by the artist entity.
-
D.
worksWithArtist
Indicates that one entity collaborates or engages in professional work with an artist.
-
E.
partnerOfArtist
Indicates a relationship where one entity is the romantic or life partner of an artist.
- 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_69f2249e19108190a458ab446096bf22 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
Created at: April 29, 2026, 8:20 p.m.