Triple
T19200599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Pete Best Band |
E470094
|
entity |
| Predicate | hasCoreAudience |
P132907
|
FINISHED |
| Object | Beatles fans |
—
|
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: Beatles fans | Statement: [The Pete Best Band, hasCoreAudience, Beatles fans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoreAudience Context triple: [The Pete Best Band, hasCoreAudience, Beatles fans]
-
A.
hasAudienceReach
Indicates the extent or scope of people or groups that are exposed to, can access, or are targeted by a particular entity, message, or activity.
-
B.
hasAudience
Indicates that an entity is intended to be received, viewed, or engaged with by a particular group of people.
-
C.
hasCorePopulation
chosen
Indicates that an entity possesses a central or primary group of individuals that constitute its main population.
-
D.
hasAudienceLevel
Indicates that something is intended for, suitable for, or targeted at an audience with a specific level of knowledge, experience, or proficiency.
-
E.
hasAudienceSize
Indicates the relationship between an entity and the number of people or size of group that receives, views, or engages with it.
- 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_69d8dd0ad9088190a173b32657ae2e7a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f997879c8190ae7618d1ba0cede9 |
completed | April 20, 2026, 10:01 a.m. |
| PD | Predicate disambiguation | batch_69e4b9bc158081908307dab01d9478c6 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:07 p.m.