Triple
T35273670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Know Yourself |
E1018738
|
entity |
| Predicate | hookFeatures |
P24936
|
FINISHED |
| Object | repeated phrase running through the 6 with my woes |
—
|
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: repeated phrase running through the 6 with my woes | Statement: [Know Yourself, hookFeatures, repeated phrase running through the 6 with my woes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hookFeatures Context triple: [Know Yourself, hookFeatures, repeated phrase running through the 6 with my woes]
-
A.
hookType
Indicates the specific kind or category of hook associated with or used by an entity.
-
B.
featuresOriginalHookBy
Indicates that an entity (such as a work or recording) includes an original hook created by the specified artist or creator.
-
C.
hookOf
Indicates that one entity functions as a hook or hooking component that is part of, attached to, or used by another entity.
-
D.
shellFeature
Indicates that one entity functions as a characteristic or structural feature of another entity’s shell.
-
E.
hasHook
chosen
Indicates that one entity possesses, is equipped with, or features a hook in relation to another entity or context.
- 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_69f76de5c4788190896ad598ae7d6bc6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78fa2952881909b5d0c96f64a1685 |
completed | May 3, 2026, 6:10 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.