Triple
T10621528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2014 Forest Hills Drive |
E250214
|
entity |
| Predicate | hasGuestFeatures |
P93602
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [2014 Forest Hills Drive, hasGuestFeatures, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGuestFeatures Context triple: [2014 Forest Hills Drive, hasGuestFeatures, false]
-
A.
hasGuestVocalists
chosen
Indicates that one or more guest vocalists perform vocals on a work, performance, or recording in addition to the primary artist(s).
-
B.
hasNotableGuest
Indicates that an entity has a guest who is distinguished, prominent, or otherwise noteworthy in some significant way.
-
C.
hasGuestVerseBy
Indicates that a work (such as a song or track) includes a guest verse performed by a specified artist.
-
D.
hasRemixFeaturing
Indicates that an original work has a remix version that features an additional artist or artists not present in the original.
-
E.
hasAudioFeature
Indicates that one entity possesses or is associated with a specific audio-related characteristic or property.
- 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6df70b0288190bf6edd705632ff02 |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7a223c8190854409d76368f3e8 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 8:50 p.m.