Triple
T33267103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Be Right There |
E851680
|
entity |
| Predicate | usesHookFrom |
P151582
|
FINISHED |
| Object | Don't Walk Away |
—
|
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: Don't Walk Away | Statement: [Be Right There, usesHookFrom, Don't Walk Away]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesHookFrom Context triple: [Be Right There, usesHookFrom, Don't Walk Away]
-
A.
hasHook
Indicates that one entity possesses, is equipped with, or features a hook in relation to another entity or context.
-
B.
hookOf
Indicates that one entity functions as a hook or hooking component that is part of, attached to, or used by another entity.
-
C.
featuresOriginalHookBy
chosen
Indicates that an entity (such as a work or recording) includes an original hook created by the specified artist or creator.
-
D.
usedVia
Indicates that an entity performs or achieves something by means of, or through the use of, another entity or mechanism.
-
E.
primaryHook
Indicates that one entity serves as the main or principal connection point, attachment, or linkage for another entity within a given structure or system.
- 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_69f349642dac81908a37ffcc3b976a55 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:32 a.m.