Triple
T1235399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fantasy |
E26535
|
entity |
| Predicate | hookDescription |
P11875
|
FINISHED |
| Object | catchy, instantly recognizable chorus |
—
|
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: catchy, instantly recognizable chorus | Statement: [Fantasy, hookDescription, catchy, instantly recognizable chorus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hookDescription Context triple: [Fantasy, hookDescription, catchy, instantly recognizable chorus]
-
A.
hasDescription
chosen
Indicates that an entity is associated with a textual description that explains or characterizes it.
-
B.
symbolDescription
Indicates that a symbol is associated with or defined by a particular descriptive explanation or meaning.
-
C.
describedIn
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
-
D.
flagDescription
Indicates that a textual explanation or label is provided describing the meaning, purpose, or status represented by a particular flag.
-
E.
describes
Indicates that one entity provides an explanation, representation, or account of another entity or concept.
- 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_69a4948571c88190a9191e451e6035fd |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be5e421081908f2432528019db25 |
completed | March 1, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69a4bb67d52c8190815d6356b79d6ed5 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.