Triple
T23932487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Wailers Band (post-Marley line-ups) |
E602537
|
entity |
| Predicate | hasLineupCharacteristic |
P140282
|
FINISHED |
| Object | frequent personnel changes |
—
|
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: frequent personnel changes | Statement: [The Wailers Band (post-Marley line-ups), hasLineupCharacteristic, frequent personnel changes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLineupCharacteristic Context triple: [The Wailers Band (post-Marley line-ups), hasLineupCharacteristic, frequent personnel changes]
-
A.
partOfLineup
Indicates that an entity is included as a member or component within a particular lineup or roster.
-
B.
basedOnLineupsOf
Indicates that something is derived from, determined by, or constructed using specific lineups.
-
C.
hasPerformerCharacteristic
Indicates that a performer possesses a particular attribute, quality, or characteristic.
-
D.
usesLineCharacteristic
Indicates that one entity employs or is based on a specific characteristic or property of a line.
-
E.
hasCrewCharacteristic
chosen
Indicates that a crew possesses a specified attribute, quality, or defining feature.
- 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_69e2953cf6e081909b8e25a10a52dddc |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1cf9ce6b8819093fc5e44b1ed137f |
completed | April 29, 2026, 9:30 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:58 p.m.