Triple
T34043295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Artimus Pyle Band |
E873008
|
entity |
| Predicate | hasCoreRepertoire |
P143382
|
FINISHED |
| Object | Lynyrd Skynyrd classics |
—
|
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: Lynyrd Skynyrd classics | Statement: [The Artimus Pyle Band, hasCoreRepertoire, Lynyrd Skynyrd classics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoreRepertoire Context triple: [The Artimus Pyle Band, hasCoreRepertoire, Lynyrd Skynyrd classics]
-
A.
hasCorePopulation
Indicates that an entity possesses a central or primary group of individuals that constitute its main population.
-
B.
hasCore
Indicates that one entity possesses, contains, or is built around a central or most essential component represented by another entity.
-
C.
hasCoreMember
Indicates that an entity includes another entity as a central or primary member of its group, organization, or structure.
-
D.
hasCoreValue
Indicates that an entity possesses or is characterized by a fundamental guiding principle or core belief.
-
E.
associatedRepertoire
chosen
Indicates a relationship where one entity is linked to or connected with a particular repertoire, such as a set of works, skills, or performances.
- 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_69f349a3363081909cea4c9a848cefe2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:51 a.m.