Triple
T15164911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Early Song |
E362309
|
entity |
| Predicate | hasReceptionType |
P99589
|
FINISHED |
| Object | cult following |
—
|
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: cult following | Statement: [Early Song, hasReceptionType, cult following]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReceptionType Context triple: [Early Song, hasReceptionType, cult following]
-
A.
hasReception
Indicates that an entity hosts, includes, or is associated with a reception event (such as a formal gathering or welcoming function).
-
B.
hasTypeOfRecipient
Indicates that an entity is associated with a specific category or kind of recipient it is intended for or directed to.
-
C.
hasAcquisitionType
Indicates the specific kind or category of acquisition relationship that exists between one entity acquiring another.
-
D.
workHasReception
chosen
Indicates that a work (such as a creative or scholarly work) has an associated reception, capturing how it has been received, evaluated, or responded to by audiences or critics.
-
E.
hasReceiver
Indicates that an entity serves as the recipient or target of something provided, sent, or directed by another entity.
- 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_69d85a087b7c81908baa94a53dac8d68 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0064b21ac81908b793bdbd741bcd8 |
completed | April 15, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69deb9779acc81908ed2dad382c42dca |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:08 a.m.